Evidence Contract
What is admissible, current and reproducible.
Evidence classes, source rules, freshness, cut-off, exception handling and replay requirements.
From SOP to governed operation
Learn it. Test it. Ratify it. Run it. Replay it.
Macrovision separates model assistance from operating authority. AI may reconstruct declared and observed process, but deterministic contracts, customer ratification, replay evidence and effective human mandates decide what can enter a Treasury Case.
Six stages
The onboarding work becomes part of the proof.
Macrovision records where each process claim came from, what changed during challenge and which historical cases support the final graph. That prevents a polished process diagram from hiding uncertain authority or exceptional practice.
| Stage | Input | Output | Gate |
|---|---|---|---|
| 1. Discover | SOPs, policies, approval matrices, templates and completed cases. | Declared and observed SOP Twins with citations and confidence. | Contradictions and material questions remain open. |
| 2. Contract | Resolved evidence, policy, roles, sequence, exceptions and integrations. | Candidate Evidence, Decision, Operating, Connector and Authority Contracts. | No executable prose or undeclared side effect. |
| 3. Compile | Content-addressed candidate contracts. | Finite deterministic plan and compiler receipt. | Reject missing roles, failure paths, cut-offs, bounds or safe operations. |
| 4. Replay | Frozen historical cases and expected traces. | Virtual-clock replays and declared-versus-observed conformance. | Material deviations require resolution or contract revision. |
| 5. Ratify | Reviewed contract and validation evidence. | Customer signatures and effective activation record. | Authority, mandate and segregation checks must pass. |
| 6. Operate | Approved trigger or material event. | Treasury Case, familiar artefact, Decision Packet and monitoring. | Writes remain bounded, idempotent, revocable and reconciled. |
Portable contract stack
Each kind of authority has one owner.
A customer should be able to export the exact contract and packet behind a decision. Portability makes the evidence, process and authority legible even without the Macrovision interface.
Decision Contract
What economic outcome the institution is testing.
Objective, constraints, loss function, policy thresholds and materiality.
Treasury Operating Contract
Who acts, in which sequence and under which exceptions.
Triggers, roles, steps, deadlines, artefacts, approvals, escalation and reopen rules.
Connector Contract
Which external operation is permitted.
Named operation, opaque credential reference, idempotency, retries, revocation and reconciliation.
Authority Contract
Who may ratify, activate, approve, override or withdraw.
Effective assignments, mandates, permissions and segregation of duties.
Decision Packet
What happened and how to reproduce it.
Frozen inputs, exact contracts and methods, receipts, rationale, signatures, audit anchors and reopen conditions.
Controlled side effects
Every write is an intent before it is an effect.
The case runtime emits a bounded operation. The connector gateway checks its declared permission and deterministic idempotency identity, places it in a transactional outbox, records the provider receipt and reconciles the result. A retry cannot silently duplicate the intended effect.
Make the current process inspectable
The first conversation is about one recurring decision, not a platform migration.
Contract and replay artefacts establish declared behaviour and technical integrity. They do not substitute for a customer’s legal, regulatory, risk or approval obligations.