Knowledge Structure Law (KS-LAW)

Version: 1.0 Effective: 2026-02-15 Authority: Owner (via P27) Status: ACTIVE

---

§1: Frozen Structure Definition

The Knowledge Hub uses a 4-folder structure under knowledge/. This structure is FROZEN — no new top-level folders may be created.

knowledge/
├── dev/                  # Tier 1: Foundation + Development
│   ├── blueprints/       # Architecture plans, feature designs
│   ├── ssot/             # Constitution, laws, SSOT documents
│   └── reports/          # Dev reports, audits
│
├── current-state/        # Tier 2: Live System State
│   └── *.md              # Current status snapshots (firebase, gpt, playwright)
│
├── current-tasks/        # Tier 2: Active Work Items
│   └── *.md              # Tasks in progress
│
└── other/                # Tier 3: Operations + Archive
    ├── archive/          # Old/completed items, migration logs
    ├── decisions/        # Decision records
    ├── guides/           # Context packs, playbooks, templates
    │   ├── context-packs/
    │   ├── playbooks/
    │   └── templates/
    ├── processes/        # How-to guides, setup procedures
    ├── research/         # Research notes, investigations
    ├── sessions/         # Session reports (ALL sessions go here)
    ├── specs/            # Technical specifications
    ├── sprints/          # Sprint planning docs
    └── status/           # System status, health checks, inventories

§2: Allowed Top-Level Folders

Folder	Purpose	Mutable?
dev/	Foundation documents, blueprints, SSOT	Sub-folders allowed
current-state/	Live system status snapshots	Flat (no sub-folders)
current-tasks/	Active work items	Flat (no sub-folders)
other/	Everything else: operations, archive, specs	Sub-folders allowed

Any folder not in this list is a VIOLATION.

§3: Rules for AI Agents

1. NO NEW TOP-LEVEL FOLDERS: Agents MUST NOT create folders outside the 4 listed above. If a document doesn't fit, put it in other/ with an appropriate sub-folder.

2. SESSION REPORTS: ALL session reports MUST go in knowledge/other/sessions/. NOT in operations/sessions/, NOT in ops/, NOT in any other location.

3. Health checks and status: Go in knowledge/other/status/.

4. New sub-folders under other/: Allowed, but must be semantically distinct from existing ones. Prefer using existing sub-folders.

5. If unsure: Put the document in knowledge/other/archive/ and flag for human review.

6. Request new top-level folder: Only the Owner can approve new top-level folders. Agent must ask explicitly and explain why existing folders don't work.

§4: Validation

The Health Check workflow (sync-check.yml) validates this structure every 6 hours:

• CHECK 7: Lists all top-level folders under knowledge/
• Compares against allowed list: dev, current-state, current-tasks, other
• Any folder not in the list → FAIL

§5: History

Date	Event
WEB-50 (2026-02)	Original 3-tier structure created
WEB-62 (2026-02-10)	Restructured to 8 folders
WEB-65 (2026-02-10)	Consolidated to 4 folders (FROZEN)
P27 (2026-02-15)	Enforcement law created, 7 rogue docs moved