Client Delivery › The Client Plane: PLAN
The Client Plane: PLAN
The only per-client build. This page mirrors the client column of the architecture diagram, band for band:
the seven sections below are the same C1 to C7 you see there, in the same order. Each row is one value the client fills in. "Filled by" names the
Client Discovery section that gathers it; "Takes effect" says when a change lands. No code ever enters the plane; custom logic is built in the
Solution layer and selected here.
PLAN: the assessment that fills the binding
Six assessment domains, borrowed from enterprise-architecture practice without the ceremony. The rule: every finding becomes a value below, an overlay selection, or a promotion candidate. Anything else is out of scope, and the record says so.
| Assessment domain | What it examines | Lands in the binding as | Discovery sections |
|---|---|---|---|
| Business capability mapping | The client’s capabilities mapped onto the Knowledge layer’s capability register, which use cases exist, which patterns, what automation heat | use-case selection · agent activation list | A |
| Application architecture | The client’s systems mapped to MCP servers and tools | source_connectors[] · tool exposure per agent | D |
| Data architecture | Their sources mapped to the table-group taxonomy plus the authority ranking | source mappings · authority overrides | D |
| Integration architecture | Connector and gateway configuration: sync modes, frequencies, formats | sync modes · schedules · formats | D |
| Infrastructure architecture | Region, residency, account model, capacity expectations | residency · tenancy model · budgets | E, H |
| Security architecture | Identity, permission scopes, gates, confidentiality routing | idp_config · scopes · gate_name_mapping · approvers | E, F |