reference · Company
Library Index & Roadmap
Library Index & Roadmap
Purpose
Provide a human-readable map of the Blinto SOP Library, identify the canonical document for each operating domain, and maintain the prioritized list of missing documents without creating blank placeholder files.
GitHub main is the canonical source. This index is navigation and planning metadata; it must not duplicate the operating instructions owned by the linked documents.
Document Types
- SOP — repeatable process: how work is performed.
- Policy — company rule or required boundary.
- Checklist — execution/verification aid linked to a governing SOP or standard.
- Template — reusable structure for creating a recurring artifact.
- Guide — instructional guidance where judgment/adaptation is expected.
- Reference — stable information, taxonomy, standard, map, migration register, or lookup resource.
Governance & Authoring
| Canonical document | Type | Domain |
|---|---|---|
| Library Standard | Reference | Library architecture, metadata, quality and anti-duplication rules |
| Contribution & Approval | SOP | Contribution, review and approval workflow |
| AI Authoring Workflow | Guide | AI-assisted search-before-create and drafting workflow |
| AI Instructions | Reference | Machine-facing repository authoring instructions |
| Migration Register | Reference | Legacy-source reconciliation and migration boundary |
People Lifecycle
| Canonical document | Type | Domain |
|---|---|---|
| People Lifecycle | Reference | Map of the employee lifecycle and canonical handoffs |
| Hiring | SOP | Hiring process and approval flow |
| Job Description Template | Template | Role definition for recruitment |
| Interview Scorecard Template | Template | Evidence-based candidate assessment |
| Employee Onboarding | SOP | New-joiner onboarding process |
| Employee Onboarding Checklist | Checklist | Onboarding execution verification |
| Performance Review | SOP | Performance-review operating process |
| Internship Program | SOP | Paid/unpaid internship lifecycle |
| Employee Offboarding | SOP | Departure and access/ownership closeout |
| Employee Offboarding Checklist | Checklist | Offboarding execution verification |
Workday & Leave Policies
| Canonical document | Type | Domain |
|---|---|---|
| Office Hours Policy | Policy | Normal workday, breaks and schedule routine |
| Attendance Policy | Policy | Attendance, punctuality and attendance records |
| Overtime Policy | Policy | Approved work beyond normal hours and compensation |
| Leave & Time-Off Policy | Policy | Leave entitlements, auto/manual approval boundaries and carry-forward rules |
| Leave Request & Handover | SOP | HRMS request, notification, exception review and work handover workflow |
Security & Access
| Canonical document | Type | Domain |
|---|---|---|
| Access Provisioning & Deprovisioning | SOP | Company/client access lifecycle, least privilege, reviews and removal |
| Credential & Password Management Policy | Policy | Password managers, MFA, credential storage/sharing, rotation, recovery and compromise response |
| WordPress Security Standard | Policy | Baseline WordPress security requirements |
| WordPress Security Checklist | Checklist | Baseline implementation/verification |
| WordPress Monthly Security Maintenance Checklist | Checklist | Recurring WordPress security maintenance |
Operations & Assets
| Canonical document | Type | Domain |
|---|---|---|
| Company Equipment & Asset Management | SOP | Physical asset intake, assignment, custody, repair, transfer, return and disposal |
| Incident Escalation | SOP | Severity, ownership, escalation, communication, resolution and post-incident review |
Client Delivery
| Canonical document | Type | Domain |
|---|---|---|
| Client Onboarding | SOP | Confirmed engagement to delivery-ready client setup |
| Project Kickoff | SOP | Delivery-ready engagement to aligned active project with scope, owners, milestones, risks and next actions |
| Client Access Collection | SOP | Secure identification, request, receipt, verification and closeout of client system access |
| Client Communication & Escalation | SOP | Client communication ownership, response expectations, decision logging and delivery escalation |
| Deliverable QA & Approval | SOP | Risk-based QA, findings, approval and client/release readiness gate |
| Project / Client Offboarding | SOP | Final delivery, ownership/access handoff, recurring-work closeout, records and formal engagement closure |
Information Organization
| Canonical document | Type | Domain |
|---|---|---|
| Google Drive Organization Standard | Reference | Drive placement, organization and canonical-source rules |
SEO
| Canonical document | Type | Domain |
|---|---|---|
| SEO Client Intake & Routing | SOP | Initial SEO opportunity classification and routing |
| SEO Client Intake Checklist | Checklist | Intake information and routing verification |
Integrity Audit Status
The first structural integrity audit was completed after Priority 2.
The audit:
- removed superseded duplicate office-hours/attendance and WordPress security documents;
- aligned the Library Standard's frontmatter and relationship examples with the live taxonomy;
- indexed the Migration Register;
- reconciled stale migration references;
- confirmed GitHub
mainas the canonical source for the future website and Google Drive mirror.
Future audits should check broken links, metadata values, duplicate concepts, orphaned documents, stale roadmap entries, and website-build validation automatically where possible.
Legacy Migration Status
The original SOP Library migration baseline is substantially complete. Legacy files should not remain as competing operational documents merely for history; Git history preserves prior Markdown versions.
The Employee Handbook remains an additional migration/reference source, not an approved source of truth. Its useful content should be migrated concept-by-concept and reconciled with approved decisions.
The two deleted security spreadsheets remain explicitly excluded from the migration/reference set.
Missing SOP Roadmap
A roadmap item means the capability should exist; it does not authorize inventing company rules. Before creating any item, search the library for an existing canonical owner and gather the actual operating decisions required.
Priority 1 — Company-wide operational foundations
Complete.
Priority 2 — Client delivery foundations
Complete.
Priority 3 — Website delivery
- Website Project Intake & Technical Discovery.
- Staging-to-Production Website Launch.
- Website Launch QA Checklist.
- DNS Change & Domain Launch.
- Website Backup & Restore.
- Website Maintenance / Update Process.
- Website Incident / Emergency Response.
Priority 4 — SEO delivery
- Website SEO Audit — currently referenced by SEO Intake but not yet canonicalized.
- Website Architecture & SEO Planning — currently referenced by SEO Intake but not yet canonicalized.
- Keyword Research & Mapping.
- On-Page SEO Implementation.
- Technical SEO QA.
- SEO Reporting & Review.
Priority 5 — People supporting processes
- Probation Review — only if operationally distinct from the canonical Performance Review process.
- Leave Handover Checklist — only if the leave process demonstrates independent reusable value.
- Corrective / Performance Improvement Process — requires explicit People/leadership rules before drafting.
- Employment/Internship document templates — offer, appointment, internship agreement, certificate or recommendation templates only after current legal/HR wording is approved.
Do Not Create Yet
Do not create a document merely because it appears on the roadmap. Specifically avoid:
- blank placeholder Markdown files;
- separate SOPs for each tool when one process can own the behavior;
- client/company-specific duplicates of a generic process;
- policy wording inferred from old habits without approval;
- templates containing legal, compensation, or employment promises without current approved wording;
- downstream SEO SOPs solely from references in another document.
Roadmap Maintenance
When a roadmap item is created and approved:
- remove it from the missing list;
- add it to the appropriate canonical index section;
- link related documents rather than duplicating their rules;
- update documents that currently reference the capability only generically;
- verify no older document still claims ownership of the same concept.