Structured request
Bind tenant, human, agent, workload, delegation, purpose, decision, subject, time, and evidence profile.
Use neutral, testable requirements to determine whether ECG, an alternative platform, a combined stack, an integrator, or an internal build can satisfy the evidence transaction.
Define the current inability to show what an agent was permitted to see, which assertions were valid and knowable, which sources were authoritative, what evidence was missing or contradictory, and whether the state can be verified and replayed.
Equivalent artifacts and implementations should be eligible when they satisfy the complete, tested mission need.
Bind tenant, human, agent, workload, delegation, purpose, decision, subject, time, and evidence profile.
Enforce the intersection of human, agent, workload, source, purpose, classification, residency, and disclosure policy.
Distinguish valid time from what was observed, recorded, superseded, and knowable.
Apply explicit source authority, freshness contracts, mandatory evidence, contradictions, and gaps.
Produce a versioned Evidence Manifest and signed Context Bundle with obligations and expiration.
Support detached verification, content-addressed integrity, declared replay fidelity, and export.
“Roadmap” and “can build” should not count as current capability unless schedule and contract make delivery enforceable—but ECG’s own roadmap receives the same treatment.
Describe the operational inability to reconstruct authorized and sufficient evidence. Do not begin with the ECG brand.
Separate mission-, security-, interoperability-, and schedule-essential capabilities from preferences and future options.
Evaluate search, graphs, catalogs, policy, observability, operational platforms, integrators, combinations, and internal build.
Give every vendor the same identity, time, permission, contradiction, missing-evidence, signature, and replay test.
Analyze price, scope, outcomes, alternatives, internal build, transition, and negotiated protections.
Require export, detached verification, documented interfaces, customer data ownership, and future market reassessment.
Public demonstrations, prototypes, reference architectures, and planned capabilities are different states.
The downloadable Markdown package contains neutral worksheets and acceptance structures that procurement, technical, security, legal, and audit teams can adapt.
No. The buyer selects the authority, conducts market research, obtains approvals, evaluates alternatives, and determines price reasonableness. This center supplies a factual evaluation structure.
It may solve part of it and should be evaluated. The common test asks whether a system also binds purpose and workload identity, preserves excluded and missing evidence, supports bitemporal reconstruction, and produces a signed, replayable artifact.
No. Any intellectual-property claim must be verified by counsel, mapped to shipped capability, and considered only alongside mission need, alternatives, responsibility, schedule, and price.
One bounded decision type, a small source set, explicit acceptance tests, security review, signed artifacts, verification, replay, portability, and transition rights.
Require documented schemas, data export, detached verification, customer-controlled evidence and keys where appropriate, third-party connector interfaces, and market reassessment before expansion.
We will separate public material from patent-sensitive, security-sensitive, and customer-confidential evidence.