Editable Markdown · Version 1
Data product contract
Agree the consumer promise before publishing a dataset, API or knowledge product.
- Purpose and consumers. Decision supported; named consumers; supported and unsupported uses.
- Meaning and grain. Business key, units, currency, dates, definitions, joins and adjustment rules.
- Interface and version. Supported query/API/index, examples, compatibility and notice period.
- Rights and authority. Source rights, tenant/entity boundary, permissions, retention and enforcement points.
- Quality and freshness. Critical tests, reconciliation, measurement clock, cutoff and stale-data response.
- Operation and ownership. Business owner, run contact, incident route, recovery and review date.
See the synthetic example
Invoice Lines v1 is a synthetic analytical product, one row per invoice line and declared version. Amounts retain currency and legal entity. A derived balance aggregates compatible inputs before joining. Publication waits when required reconciliation is missing; a stale version is usable only within its approved consumer window.
Editable Markdown · Version 1
AI request context record
Identify the trusted facts and declared intent needed before a retrieval or tool call.
- Identity references. Verified user/workload references, tenant and authoritative attribute sources; minimize personal details.
- Intent and target. Task and resource scope; distinguish user assertions from verified facts.
- Meaning and sources. Product/version, currency, cutoff, source references and freshness requirements.
- Authorization. Trusted policy decision reference, permitted resources, audience, expiry and recheck conditions.
- Clarify, refuse or fall back. Missing mandatory context, ambiguous intent, revoked rights, stale source and unavailable policy service.
- Evidence and lifecycle. Protected record location, retention, deletion, owner and change trigger.
See the synthetic example
A synthetic employee asks why INV-100 is held. The application verifies identity and entity scope, resolves the current invoice and permitted policy sources, and records the policy decision reference. The model cannot infer an entitlement from department, tone or the sample JSON. Changing the hold requires a separately authorized command.
Editable Markdown · Version 1
Workflow release evidence
Make a go, hold or stop decision from inspectable results and named responsibilities.
- Scope and build. Workflow purpose, users, dependencies, model/prompt/tool/product versions and exclusions.
- Evaluation. Expected and actual behavior for useful requests, ambiguity, access denial, stale data and recovery.
- Action controls. Typed commands, exact-payload approval, current authority/state checks and uncertain-write reconciliation.
- Operating readiness. Monitoring, cost/latency limits, incident owner, fallback, rollback and consumer instructions.
- Decision and conditions. Authorized approver, go/hold/stop, evidence references, unresolved gaps and review trigger.
- Continuing assurance. Material change, rights change, source degradation, incident and retirement triggers.
See the synthetic example
The synthetic invoice assistant explains a dated balance of 500 and a later balance of 300 under the example definition. It must deny unauthorized entity access and reject an expired action approval. These are expected outcomes only: the supplied evidence CSV marks every actual result not run.
