QiAccess Start Master Blueprint
This repository is the active master blueprint for QiAccess Start.
QiAccess Start is Cody's cognitive front door:
- Home
- Start
- Capture
- Knowledge
- Memory
- Insights
- System
The old QiOS material is not discarded, but it is no longer allowed to compete with the active doctrine. Useful governance, standards, registry discipline, and architecture policies remain in force. Legacy multi-tenant and client-platform assumptions are retained only as quarantined reference material until they are explicitly revalidated.
Active Doctrine
- QiAccess is the portal.
- The map is the interface.
- The knowledge base is the memory behind each node.
- Capture must stay fast or the system fails.
- System is nested administration, not a top-level junk drawer.
- Memory and Insights stay honest when they are placeholders.
Current Phase
Phase 1 remains stabilization and prototype flow validation:
- keep the SPA working
- align the app to the seven roots
- preserve working launcher and link behavior
- freeze legacy surfaces in place
- validate Capture as the first real operating path
What Stays Authoritative
docs/01_governance/: principles, policies, registry, and ADR disciplinedocs/02_architecture/: active QiAccess Start system model and runtime framingdocs/06_applications/: the seven-root portal doctrinedocs/08_appendices/20_legacy/: quarantined legacy material and salvage notesstandards/andregistry/: retained structural controls that still serve the active system
Build Loop
The blueprint can still be maintained through the existing documentation toolchain:
- update doctrine or registry files
- run
rebuild.bat - inspect validation output
- preview with
mkdocs servewhen needed
Legacy Handling
Use the quarantine appendix before promoting older QiOS, QiOne, tenant, client, or product-delivery doctrine back into the active blueprint:
docs/08_appendices/20_legacy/legacy_salvage.mddocs/08_appendices/20_legacy/qiaccess_start_legacy_quarantine.md