Candidate
Proposed, source-linked and challengeable.
No production authority. Missing evidence and unresolved deviations remain visible.
Trust centre
Authority is explicit, bounded and replayable.
Macrovision is designed so a model-generated suggestion, an analytic result and a system integration cannot acquire customer authority by implication. Every authoritative step must resolve through exact contracts, effective people, evidence and receipts.
Control planes
The workflow can act only where several boundaries agree.
Passing one check never bypasses another. Organisation scope, evidence admissibility, economic policy, workflow state, connector permission and human authority are independent gates that bind to the same Treasury Case.
| Boundary | Control | Failure behaviour | Portable evidence |
|---|---|---|---|
| Institution | Mandatory organisation and legal-entity scope on records and principals. | Opaque denial; legacy unscoped rows remain quarantined. | Case and event scope. |
| Evidence | Class map, source admissibility, lineage, knowledge cut-off and expiry. | Safety-critical gaps suppress; permitted exceptions hold for authority. | Frozen evidence receipt. |
| Process | Closed action vocabulary, finite graph, roles, failure paths and bounded retries. | Compiler rejects the Operating Contract. | Compiler receipt and plan hash. |
| People | Effective assignments, mandate, permission, quorum and segregation of duties. | Approval or activation is denied without mutation. | Authority evaluation receipt. |
| Integration | Named operation, opaque credential reference, idempotency and reconciliation. | Out-of-scope and financial operations are denied. | Outbox and provider receipts. |
| Memory | Approval-time packet sealing and read-only retrieval. | Anchor mismatch fails integrity verification; the packet is not re-signed. | Canonical packet, hashes and signature status. |
Separate signatures
System integrity is not customer consent.
A content hash proves that bytes are unchanged. A YieldGuard system signature can prove which service sealed those bytes. A customer decision signature must resolve to the customer’s own authorised principal, mandate and key. Macrovision labels the absence or type of each signature instead of allowing one to stand in for another.
Macrovision Lab
Methods and workflows begin without production authority.
The Lab holds the Method Registry, Operating Contract Studio, replay fixtures, conformance results and promotion evidence. Candidate status remains visible until every required gate is evidenced; promotion controls stay unavailable when a blocker exists.
Ratified
Customer-approved contract identity.
The exact hash and version have customer authority, but permitted execution mode may still be shadow.
Active
Bounded operation under current controls.
Activation is effective-dated, revocable and limited to named scope and operations.
Withdrawn
No new case authority.
Historical packets and replay evidence remain available without reviving the contract.
Due diligence
A workflow diagnostic can begin without granting Macrovision a live connector or production approval authority.
YieldGuard provides technology and research, not legal, tax or investment advice. Security, availability, assurance and regulatory representations apply only where expressly stated in an executed agreement or published independent report.