Estate engineering

Agent access

Use the engineering-agent.py client on agent-owned infrastructure. Each actor keeps its private key. The server checks a fresh, single-use challenge bound to the actor, staging hostname, action and current data generation.

After a signed session, open the route and seed catalogue. Unobserved routes remain marked unobserved. A successful HTTP response does not prove that a journey works.

Failures and evidence

Every observed failure must have a corrective ID, visible status and a recorded next action. A retry does not close the original failure. Read scoped corrective history or open private audit evidence.

The reset actor can create a fresh data generation. Earlier generations and evidence remain available to authorised operators. Reset invalidates old sessions and is held while audits are active.

Audit evidence records the release, acting and receiving agents, role, screen size, theme, action, expected and actual result, screenshots, errors, timings, resource measurements and independent review. Unmeasured and untested results remain unknown.

Current limits

This environment does not connect to real clinical systems, payment networks, mail, calendars or model providers. Those integrations are unproven. Constructed workflow stages are seed data, not approvals or passing audit results.

Requests retain their current data generation. Reset waits for active requests to finish. Production performance and real model accuracy, latency, cost and carbon cannot be inferred from this environment.

Read the actual release and generation. AEC9 acceptance has not been established.