Inspect Payne’s architecture

Components and ownership

• Visitor browser — Renders public UI Owner: visitor.
• Hosted Next.js — Landing, docs, guided simulation Owner: Payne application.
• Versioned fixture — Checked-in simulation evidence Owner: repository.
• Payne web — Local workspace and server actions Owner: Payne application.
• Payne worker — Durable jobs and monitoring Owner: Payne application.
• PostgreSQL — Payne durable state owner Owner: Payne.
• DataHub + MCP — Current catalog facts and bounded reads Owner: DataHub.
• Inference provider — Bounded interpretation Owner: configured provider.
• Official sandbox — Bounded application and re-ingestion Owner: Payne local-live.

Relationships

1. The visitor opens the hosted Next.js application.
2. Hosted simulation reads a checked-in fixture and has no live service connection.
3. The visitor opens the locally running Payne web process.
4. Payne web reads and writes authorized durable product state.
5. The worker claims jobs and persists immutable evidence and outcomes.
6. Adapters discover bounded reads through MCP and use official interfaces for allowlisted application writes.
7. The worker sends bounded evidence for interpretation; the provider cannot set gate state.
8. The worker applies the accepted fixture artifact only inside the official sandbox.
9. The bounded scenario updates lineage before Payne performs a fresh read.

Components and ownership

• Current DataHub evidence — Catalog fact owner Owner: DataHub.
• Versioned evidence — Normalized immutable snapshot Owner: Payne PostgreSQL.
• Agent interpretation — Investigates and explains; no authority Owner: configured model.
• Deterministic evaluation — Computes contract and gate result Owner: Payne rules.
• Accountable human — Supplies authority-bound decision Owner: recorded owner.
• Apply and write back — Mutation response followed by fresh read Owner: Payne worker.
• Active monitoring — Worker schedules fresh evidence checks Owner: Payne worker.
• Fresh evidence delta — Changed graph, schema, or authority Owner: Payne PostgreSQL.
• Reaffirm or invalidate — Deterministic monitored outcome Owner: Payne rules.

Relationships

1. Current DataHub facts become a bounded, versioned evidence set.
2. The agent investigates only the evidence bound to the run.
3. Interpretation can inform the explanation but cannot set the result.
4. Deterministic rules identify whether accountable human authority is required.
5. The accountable human approves the exact reviewed artifact and evidence binding.
6. A mutation response is provisional until a fresh read matches; then monitoring registers.
7. The worker, not a browser refresh, collects fresh evidence on schedule.
8. Rules reaffirm current conditions or invalidate the prior approval.
9. A reaffirmed gate remains monitored; invalidation preserves the prior decision history.