AntifragileAI can propose the compliance answer. EcoKure puts a governed decision boundary around it, keeps uncertain work with a person and shows exactly what must be revisited when a rule or source changes.
Executable run · DTL runtimeThree verdicts were produced by the adapter behind this walkthrough.
Each request carries a request digest and decision digest into the signed EvidencePack. The runtime is deterministic, side-effect free and uses synthetic data only.
Measured foundation · AWS staging5 gates live in the recorded smoke
117,290 verifications, KMS signing, encrypted backup/restore and one synthetic request were recorded in the customer-owned staging run.
Verifications117,290
p95 soak8.9 ms
Losses0
The governed workflow
From a proposal to a record someone else can check.
The roles stay clear. AntifragileAI supplies the proposed compliance answer and domain context. EcoKure checks the declared control pack and preserves the evidence. A named customer reviewer decides what may continue.
01 · PROPOSE
AntifragileAI
Receives the agreed question and returns a proposed answer with its model and prompt context.
02 · CHECK
EcoKure gate
Runs deterministic checks against the released control pack and evidence requirements.
03 · DECIDE
PASS · BLOCK · REVIEW
Returns a bounded verdict. Uncertainty stays visible instead of becoming a best guess.
04 · PRESERVE
EvidencePack
Seals the request, sources, hashes, decision and reviewer path for inspection.
05 · REPLAY
Change impact
When a source changes, replay only dependency-linked work and hold the rest for review.
Buyer-safe demo
Three requests. Three honest outcomes.
Select a request to inspect the reason, controls and dependency references. These are synthetic examples of the Regenold control pack, not partner results.
AI Act compliance answer review
v0.1.0
Controlled change
regenold-change-001
↻A controlled source revision changes the transparency rule. EcoKure identifies the work that depends on it, replays only safe cases and holds uncertain interpretation for review.
Article 50 source · 2 affectedAFFECTED
regenold-q02REPLAYED
regenold-q03REVIEW QUEUE
regenold-q01PRESERVED
Pilot acceptance
Proof that maps to a decision.
A successful pilot earns a customer decision, not a marketing claim. The owner labels the sample, the reviewers inspect the pack and the record states what remains open.
Decision coverageEvery in-scope request receives PASS, BLOCK or ABSTAIN/REVIEW.
Replay correctnessOnly dependency-linked work is replayed after the controlled change.
Evidence completenessRequest, model, control pack, source versions, decision and reviewer rationale are exportable.
Boundary safetyZero cross-tenant leakage and no customer actuation in shadow mode.
Independent verificationA second reviewer verifies the EvidencePack and records GO, GO WITH LIMITATIONS or NO-GO.
Clear ownership
Everyone knows their lane.
AntifragileAI / RegenoldProposed compliance workflow, domain content and model context.
Promote the reviewed pack, customer KMS signing and retention policy into the agreed boundary.
03 · EXTEND
Change intelligence
Add DCLA/DELA, subgroup monitoring or vigilance routing only when the workflow has earned it.
04 · DISTRIBUTE
AWS Marketplace
Use Marketplace for procurement after onboarding, support, EULA, billing and update paths work end to end.
Read the boundary
Ambitious system. Exact claims.
Synthetic fixture only; no Regenold or customer data is included.
This is a product demonstration and pilot contract, not a partner acceptance or regulatory certification.
AAF provides reviewer identity and sign-in; it does not validate the model, rule interpretation or evidence.
The AWS record is target-environment staging evidence. External HTTPS ingress, independent two-principal isolation and image finding remediation remain production gates.
The control pack supports a governed workflow; it does not make every model answer true or replace qualified legal, clinical or safety judgement.
Ready to make one workflow concrete?
Bring one owner, one sample and one decision that needs to be explainable. The next step is a private readiness call and a customer-approved shadow scope.
Engineering handoffThe walkthrough has an executable adapter behind it.
Inspect the deterministic proposal envelope, request and control-pack hashes, fail-closed verdicts and selective replay contract before a customer shares data.