BRIDGE language card
BRIDGE · Language card · Proposal 0.3
Before the answer becomes an action.
A short reference for the proposed notation in Mind the Gap. Its benefits have not been demonstrated. Ordinary language remains available.
- 1. What is being claimed?
- Keep the statement separate from its evidence.
- 2. What supports it?
- Name the source, what remains uncertain, and any estimate.
- 3. What depends on what?
- Show conditions and missing prerequisites.
- 4. What action is requested?
- Name who may authorize it, within what limits and for how long.
ACK[message]I received it.
UNDERSTAND[message]I report that I understand it.
AGREE[claim]I agree with the claim.
YES[action; limits; duration]I permit this named action within this scope.
NO[scope]I refuse within this scope.
WAIT[action]I request a pause. Confirm whether it stopped.
Need more? EXPAND[claim] asks for ordinary-language detail. DONE[action; evidence] claims completion and provides a result to check.
Receipt is not understanding. Understanding and agreement grant no permission. Permission does not establish completion. Silence grants nothing.
A cooling proposal, in ordinary language
The supplier’s saving depends on storing goods at 8°C. Product A has a maximum storage temperature of 5°C. Helen can decide on the purchase, but has not approved it.
cooling purchase | WAIT[purchase; storage conflict] | @ product-A/spec-v4 | ! assess relocation cost | authority: Helen, purchasing only
Helen requests a pause and a cost assessment. The system must separately confirm whether the purchase stopped. This grants no permission to purchase or relocate the goods.
The Innocence Protocol · Robert Wescott
theinnocenceprotocol.com/extras/bridge-language-card.html