# Requirements: v1.44 L2 Knowledge-Network MVP Activation

## Shipped Requirements

- ✓ `REQ-L2MVP-01`: AITP activates one explicit MVP `L2` node-family surface in
  production schemas and docs, including `physical_picture` as a real family.
- ✓ `REQ-L2MVP-02`: The MVP `L2` node/edge subset remains bounded and explicit.
- ✓ `REQ-L2MVP-03`: Operators and runtime code have a lightweight production
  path to stage or seed MVP `L2` knowledge without claiming staging is
  canonical promotion.
- ✓ `REQ-L2MVP-04`: The first seeded direction materializes real nodes, edges,
  and index rows through production code.
- ✓ `REQ-L2MVP-05`: A bounded retrieval/consultation path can return seeded
  `L2` hits and optional staging hits through production code.
- ✓ `REQ-L2MVP-06`: Staging, graph seeding, and compiled retrieval do not
  silently bypass `L4` validation or normal promotion gates.
- ✓ `REQ-VERIFY-01`: The milestone closes with a non-mocked verification path
  proving the MVP `L2` surface through production code.

## Final Traceability

| Requirement | Assigned Phase | Final Status | Evidence |
| --- | --- | --- | --- |
| `REQ-L2MVP-01` | `58` | validated | canonical/backend schemas plus active `physical_picture` docs |
| `REQ-L2MVP-02` | `58` | validated | bounded MVP contract and retrieval profile alignment |
| `REQ-L2MVP-03` | `59` | validated | `stage-l2-provisional`, `seed-l2-direction`, and public service/CLI surfaces |
| `REQ-L2MVP-04` | `58`, `59`, `60` | validated | seeded TFIM direction, CLI seed path, compiled/hygiene artifacts |
| `REQ-L2MVP-05` | `59`, `60` | validated | `consult-l2` plus isolated MVP acceptance |
| `REQ-L2MVP-06` | `58`, `59`, `60`, `61` | validated | trust-boundary docs, staging separation, acceptance on isolated kernel root |
| `REQ-VERIFY-01` | `60`, `61` | validated | isolated MVP acceptance plus full suite |
