Trust centre
The free Laboratory calculates in your browser. Lens provides public research and market context. Macrovision is a planned workspace for recurring treasury reviews and is not accepting paid engagements. Customer-data safeguards must be evidenced before an institutional workspace can open.
Available public services
The public Lab downloads its calculation engine and runs editable assumptions locally. Private accounts and hosted saved runs are not available. A normal page request still creates technical connection metadata at the hosting boundary.
Laboratory calculation inputs are not sent to an AI provider or to YieldGuard for calculation. Lens reads public snapshots; browser Lens intake and click telemetry remain disabled. Neither experience verifies your actual cash position or access to an asset.
Read the public-service Privacy NoticeMacrovision is planned and is not accepting paid engagements. The website does not provide a production customer workspace, tenant-isolation certification, an independent security assessment or a service-level agreement. Sensitive records belong in a separately agreed process when readiness gates have passed.
Check product availabilityInstitutional readiness
Security requirements are distinct from verified operational controls. The procurement record must identify the actual providers, deployment, responsible people and evidence for the agreed scope.
| Question | Present boundary | Required before institutional use |
|---|---|---|
| Hosting and separation | The documented pilot architecture is a dedicated single-customer deployment. A general multi-tenant service is not qualified. | Hosting locations, provider terms, deployment inventory and tests demonstrating isolation. |
| Access and audit | Scoped authority and governance controls exist in the implementation and synthetic fixtures. Complete operational access logging is not publicly attested. | Least privilege, approved access, revocation, privileged-read and change logging, and review evidence. |
| Encryption and recovery | HTTPS protects website transport. Application configuration acknowledgements do not establish encrypted disks or successful recovery. | Verified storage/key controls, encrypted backup inventory and bounded restore evidence. |
| AI and training | The public Lab has no external AI calculation step. Institutional AI processing and provider contracts are not established. | Named providers, approved data flows, contractual no-general-model-training terms and reviewable AI output. |
| Retention and deletion | Technical retention routes cover some data families. Append-only governance evidence needs a separately qualified offboarding procedure. | Agreed schedules, legal-hold decisions, active-store deletion tests and backup/subprocessor expiry evidence. |
| Providers and transfers | A complete institutional subprocessor and transfer register has not been published. | Purpose, access, countries, provider contracts and the applicable UK/EEA transfer assessment and mechanism. |
| Support and incidents | Public contact is available. Independent assurance and incident-response service levels are not claimed. | Named response owner, incident procedure, notification responsibilities, support scope and exercise evidence. |
Documented workflow design
The following controls describe the institutional design and synthetic conformance boundary. They do not establish a deployed customer service. Organisation scope, evidence admissibility, policy, workflow state, connector permission and human authority require separate qualification before customer use.
| 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
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.
Proposed workflow qualification
The institutional design includes method records, contract preparation, replay fixtures, conformance checks and promotion evidence. These proposed authority states do not describe a customer contract ratified or activated by the public Laboratory. Missing evidence must remain visible before any promotion.
Candidate
No production authority. Missing evidence and unresolved deviations remain visible.
Ratified
The exact hash and version have customer authority, but permitted execution mode may still be shadow.
Active
Activation is effective-dated, revocable and limited to named scope and operations.
Withdrawn
Historical packets and replay evidence remain available without reviving the contract.
Due diligence
The synthetic walkthrough shows a proposed recurring review without receiving your organisational records. Macrovision is not accepting paid engagements.
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.