Metrics · logs · traces
Health, costs, freshness, drift, audit, and runtime evidence.
Owning productBlueprint · domain
Management and observability
Humans and agents inspect one evidence mesh; only named, scoped commands may change product or system state.
Cell 3.3 · operations · control · evidence- Metrics · logs · traces to Ops · QA · Status · Wiki: project
- Ops · QA · Status · Wiki to Human / agent operator: explain
- Human / agent operator to Typed command gate: declared intent
Ops · QA · Status · Wiki
Federated perspectives over product-owned observations, shared semantics, and bounded authority.
Open layer ↘Human / agent operator
Reads the same architecture, evidence, authority, and recovery contract.
Authorized operatorTyped command gate
Scope, authority, preconditions, expected evidence, and idempotency.
Management01 · store · target Metrics · logs · traces Health, costs, freshness, drift, audit, and runtime evidence.
Owning product- 02 · perspective · mixed Ops · QA · Status · Wiki
Federated perspectives over product-owned observations, shared semantics, and bounded authority.
Open deeper layer ↘ 03 · actor · target Human / agent operator Reads the same architecture, evidence, authority, and recovery contract.
Authorized operator04 · boundary · open Typed command gate Scope, authority, preconditions, expected evidence, and idempotency.
Management
Flows
- Metrics · logs · traces → Ops · QA · Status · Wiki project
- Ops · QA · Status · Wiki → Human / agent operator explain
- Human / agent operator → Typed command gate declared intent
Management
Outcome
Give humans and agents one explainable way to observe, understand, and intentionally change the system without creating shadow schedulers, hidden database writes, or unaudited control paths.
Perspectives
| Perspective | Role |
|---|---|
| Ops | Authenticated diagnosis and named operator commands |
| QA | Tests, suites, releases, regressions, and evidence |
| Status | Bounded public service truth and incident communication |
| Wiki | Git-backed architecture, decisions, runbooks, code links, and retrieval |
| Observability | Metrics, logs, traces, costs, freshness, drift, and audit events |
These perspectives may share schemas, navigation, and knowledge. Their runtime data and authority remain owned by the relevant product.
The internal subdivision and shared envelope are defined in Management Federation. Management is a federation of three product authorities, not a common backend: JobCache Management, Internals Management, and CareerVector Management publish bounded observations into shared perspectives while retaining their own data and execution authority.
Control model
Every state-changing action is a typed command with declared authority, scope, preconditions, expected evidence, and an immutable receipt. Dashboards are projections; they do not acquire write authority merely by displaying state.
The recursive command layer is specified in Management Command Contract.
AI-native operator
The agent operator reads the same architecture and evidence as a human. It must be able to trace an alert to a module, contract, implementation, test, deployment, and permitted action. Unknown authority or missing evidence means explain and escalate, not improvise a write.
Decisions still required
- Command and approval model.
- Unified telemetry envelope and retention.
- Incident and change-management lifecycle.
- Cost, quota, budget, and capacity controls.
- How architecture drift becomes a failing quality signal.
Completion evidence
Read-only correlation from user symptom to runtime evidence, followed by a separately authorized, audited, idempotent operator action and verified recovery.