Evidence-bound Deployment Kit

The verifier compares a packet with an expected source commit supplied separately by the reviewer. It checks artifact hashes, required evidence, preview deployment bindings and explicit limits on readiness claims.

It is a bounded implementation within MOM-Z14’s Synthetic Company Deployment Kit candidate. It does not implement the complete company operating system described in that original concept.

Current evidence

Seventeen executable controls exercise valid and invalid packets. They include source drift, altered files, absent evidence, unsupported availability, path traversal and a symlink escape. Synthetic controls are identified as tests, not customer outcomes.

The proof packet contains the executable prototype, tests, a source-bound deployment receipt and a record of the isolated existing-workforce run. A separate reviewer process deliberately removed the source check to verify that the tests detect the defect.

Packet source: e1f2bbedce91519427c08b6c0a81491f7e39b50e. The website may be a later commit that publishes this frozen evidence.

• Integrity checks do not authenticate an evidence publisher or prove that its underlying claims are true.
• Tests run in a controlled internal environment. No independent institutional validation, field adoption, patent novelty or security certification is claimed.
• Existing workforce endpoints run explicit deterministic tools in an isolated checkout. This is not a demonstration of general autonomous invention.
• No license, exclusive IP right, price or production readiness is offered. Ownership, name clearance and commercial terms require review.

Possible evaluation path

A future evaluation could begin with one deployment and a jointly agreed acceptance criterion: which missing or mismatched evidence must prevent a handoff? Public partnership intake is still being prepared, so this page does not offer a license, price, or active engagement.