Company enquiry
Capture the bounded workflow, environment and desired outcome.
This is EcoKure's complete BioChangeGate pilot shape using synthetic, non-customer data. Follow the workflow from readiness through change impact, selective replay, human review and a signed EvidencePack.
All ten pilot stages are represented below. The fixture uses no customer data and does not actuate a production workflow.
Each stage leaves an artefact. The final status is deliberately not “production ready”: it is a completed demonstration with the customer pilot still to be accepted.
Capture the bounded workflow, environment and desired outcome.
Create a customer boundary with explicit ownership and scope.
Issue a tenant-scoped key once and transfer it securely.
Agree the workflow owner, source and acceptance criteria.
Version the provenance, review and evidence requirements.
Observe classifications without actuating a customer workflow.
Introduce one known revision to the reference source.
Separate affected work and replay only what is linked.
Hold uncertainty for a named qualified reviewer.
Verify the signed chain and record the next decision.
The updated reference source is compared with the baseline. Dependency-linked analyses are separated into affected, preserved and unknown sets before anything is replayed.
Every record is hash-linked and signed. The unknown set remains REVIEW because the system has no verified basis to decide it automatically.
A real pilot still needs an agreed workflow owner, source boundary, customer-controlled signing key, success criteria and written go/no-go record.
| Artefact | Demo record | Production position |
|---|---|---|
| Company enquiry | enq_demo_biochange | Persisted before notification; operator-owned |
| Tenant | tenant_demo_biochange | Customer-scoped boundary |
| API key | ek_demo_•••••••••••••••• | DEMO ONLY · NOT A LIVE CREDENTIAL |
| Control Pack | BioChangeGate v0.1 (fixture) | Customer owner and reviewer approval required |
| EvidencePack | bd1a3e909513f71603… | Signed and independently verifiable |
Start with a readiness evaluation. Keep the first path bounded, non-actuating and reviewable.