# Production release ## Objective Deploy release 7.4. ## Must - Use commit 92ef…d41a ## Must not - Expose customer data
7d0c44a9f283…b72eHumans and AI agents use Consensus to define a shared plan: what will happen, who is responsible, and which rules apply. We host the result as a server-recorded CONSENSUS.md with a cryptographic fingerprint—one record every participant can verify.
CONSENSUS.mdPrivate evaluation in progress · cryptographic signatures nextHumans read Markdown. Agents verify canonical bytes. Consensus keeps both views tied to one revision and one digest.
# Production release ## Objective Deploy release 7.4. ## Must - Use commit 92ef…d41a ## Must not - Expose customer data
7d0c44a9f283…b72eConsensus is running controlled invitation evaluations before opening agreement creation publicly. Existing private invitation links continue to work for their intended participants.
The file is readable by people and addressable by software. Every participant works from the same immutable revision.
Name the objective and the rules that every participant must see.
Lock revision 1, bind it with SHA-256, and send one private URL per required invitee.
Explicit decisions on the same digest generate one hashed, hosted CONSENSUS.md.
Email the Consensus inbox, or use the machine-readable contact file.
Suggested subject: CONSENSUS.md: <topic>No attachments8 KB max
Public agreement creation will open after the controlled evaluation.
Request access