Status
reading map
Conceptual layer
① Plant systems through ⑥ Value
Repo layer
L0 (SE platform) and L1–L6
Source
architecture section 3.5

Layer hubs

How the repo layers map to the conceptual layers

Current per-layer architecture lives here (and under ../l3/, ../l4/).

Repo vs conceptual layers

Repo layers L0–L6

Conceptual layers ①–⑥

① Plant systems

② Context

③ Analytics

④ Decision

⑤ Action

⑥ Value

L0 SE contracts

L1 connectors + Plant Box

L2 universal-repositary

L3 intelligence

L4 knowledge-reasoning

L5 closure-verification

L6 experience-integration

Section 3.5 mapping: one repo row per conceptual slice

How to read it.

  1. Conceptual ①–⑥ are the architecture story; repo L0–L6 are where code and contracts live.
  2. L1 spans ① and ② (read connectors plus Plant Box direction); L5 spans ⑤, ⑥ and AutonomyPolicy; L6 presents ⑤ and ⑥ only.
  3. Deep dives for analytics and decision sit under ../l3/ and ../l4/; the fast loop is direction under ../fast-loop/.

Build now: layer pages below plus STAMPED_ARCHITECTURE.md. Later: full fast-loop as-built on the Plant Box (D4).

View Mermaid source
flowchart TB
    %% house-style: repo-vs-conceptual-layers
    subgraph conceptual["Conceptual layers ①–⑥"]
        direction LR
        c1["① Plant systems"]
        c2["② Context"]
        c3["③ Analytics"]
        c4["④ Decision"]
        c5["⑤ Action"]
        c6["⑥ Value"]
        c1 --> c2 --> c3 --> c4 --> c5 --> c6
    end
    subgraph repos["Repo layers L0–L6"]
        direction LR
        l0["L0 SE contracts"]
        l1["L1 connectors + Plant Box"]
        l2["L2 universal-repositary"]
        l3["L3 intelligence"]
        l4["L4 knowledge-reasoning"]
        l5["L5 closure-verification"]
        l6["L6 experience-integration"]
    end
    map{{"Section 3.5 mapping: one repo row per conceptual slice"}}
    l0 -.-> conceptual
    l1 -.-> c1
    l1 -.-> c2
    l2 -.-> c2
    l3 -.-> c3
    l4 -.-> c4
    l5 -.-> c5
    l5 -.-> c6
    l6 -.-> c5
    l6 -.-> c6
    repos --> map

    classDef govc fill:#fff4d6,stroke:#c99a2e,color:#000
    classDef agentc fill:#e8f0ff,stroke:#5b7bd5,color:#000
    classDef loopc fill:#eef7ee,stroke:#4f9a4f,color:#000
    class map govc
LayerPrefer
Overall../STAMPED_ARCHITECTURE.md
L1L1-connect.md
L2L2-universal-repository.md · data plane ../L1-L2-DATA-PLANE.md
L3../l3/ — detection runtime, engines, Finding contract
L4../l4/ — normative contract · ../l4/30-as-built.md for shipped runtime
L5L5-closure.md
L6L6-experience.md
Fast loop (direction)../fast-loop/ · ownership and topics ../fast-loop/07-interfaces-and-ownership.md; each layer page above has a fast-loop section
Evolution../../research/plant-efficiency-exploration-2026-09/14-coarse-architecture.md

Status labels on layer pages: as-built · contract · direction.

Page history: last 4 changes
  1. 2026-10-07 docs(technical): rewrite layers/ and L1-L2-DATA-PLANE.md to the architecture 322bf46
  2. 2026-10-03 docs(handoff,l4): fast-loop architecture handoff, L4 procedure and ledger links, indexes 0f45a47
  3. 2026-09-27 docs(architecture): lock the agent reading path 5c06002
  4. 2026-09-25 docs(l4): agentic decision architecture, ADRs, and production hardness 8275e7c

Diagram

100%

Search the architecture