Product proof
Engineering verification is necessary but is not a customer outcome. Accordo publishes decision-relevant questions and links each answer to current evidence and its boundary.
Buyer questions
Numeric benchmark results appear only after a protocol, environment, version, date, limitation and reproduction path exist.
Commercial policy is deterministic code, not a model's judgement: a renewal at or above the threshold stops and waits for a named human.
Benchmark dimension: Invalid-decision refusal
Limit: Proven for the built-in renewal object and its single value threshold. A general policy engine over arbitrary custom objects does not exist.
Inspect evidenceThe agent cannot approve on the human's behalf. A test asserts the refusal, so the boundary is a property of the system rather than a promise in a README.
Benchmark dimension: Human authority boundary
Limit: In local-development mode the actor is asserted, not authenticated: no authentication ships, so an actor header there is not an identity. This holds a boundary against an honest agent, not against an attacker with network access.
Inspect evidenceOne command tells an agent what an application actually is — packages, capabilities, resources, actions, policies, providers — read from checked-in source, in a single deterministic JSON report.
Benchmark dimension: Independent composition inspection
Limit: Source-only and read-only. It never opens the database, contacts a provider, reads a secret, or reports runtime, CI or authorization state — and it lists those blind spots as machine-readable limitations in its own output.
Inspect evidenceZero third-party runtime dependencies. Node 22 and a checkout — no build step, no bundler, no framework underneath your framework.
Benchmark dimension: Source portability and hosted-runtime independence
Limit: Development dependencies and the eventual PostgreSQL adapter are separate questions. Having no runtime dependencies is a property of the framework, not of whatever you add on top of it.
Inspect evidenceBenchmark architecture
A synthetic run is never presented as customer evidence. Where no equivalent baseline exists, comparisons cover architecture, responsibility and verification rather than invented competitor numbers.