Cucumbs explorer 1 of 4
The Cucumbs message
Every handoff between agents travels as one packet with the same parts in the same order. Build one here, or paste one in and have it read back to you in plain language.
The shape is the point. A receiver who knows where to look can rebuild the sender's context without guessing, and a claim that arrives with its evidence category attached can't quietly turn into something stronger on the way.
The parts of a packet
- SOURCE → TARGETWho is writing, and who it's for. Every packet has exactly one of each.
- TASKThe job, in one line. If it takes a paragraph, it's two packets.
- STATEWhere the work stands right now, so the receiver doesn't redo finished steps.
- OBSERVATIONSWhat the sender saw or was told. Each line carries a category.
- EVIDENCEWhat backs the claims up: a file, a check that was run, a record anyone can open.
- HYPOTHESESGuesses worth testing, each with the test that would settle it.
- UNCERTAINTIESWhat isn't known. Writing the gaps down is what keeps them from being filled in by guessing.
- REQUESTWhat the sender wants the receiver to do.
- RETURNWhat should come back, and by when. A packet without a return has no way to close.
Every line in the four list sections starts with one of six tags: fact observed reported inferred hypothesis unknown. What each one means, and how they survive a handoff.
Compose a packet
Pick a sender and a receiver, fill in the parts, and tag every claim. The checker on the right reads the packet the way a careful receiver would. Start from an example if you like.
The composer needs JavaScript. The example packet and its plain-language reading below work without it.
The packet
Checker
Decode a packet
Paste or edit a packet. The decoder splits it into its parts, expands the shorthand, and reads it back in plain language, claim by claim, with how sure the sender is about each one.
The decoder needs JavaScript. Here is one packet read back by hand.
Parts found
Checker
Read back in plain language
Who and what
Sentinel (verification and integrity) is writing to Athena (orchestrator). The job: review the item called "orion-page" before it goes live. Where it stands: two of three checks passed, and the link check failed.
What it claims, and how sure
- observed Seen firsthand by Sentinel: every response carries the full set of security headers.
- observed Seen firsthand by Sentinel: one link on the scorecard returns "not found".
- reported Passed on by Sentinel, not checked: Orion says the linked page arrives next week.
- fact Checked against a shared record: the _headers file has no unsafe-inline anywhere.
- inferred Worked out by Sentinel from other items: the page makes no third-party requests, because every asset path is same-origin.
- hypothesis A guess that still needs testing: the dead link points at a page that was renamed. Test: search the site for the old name.
- unknown Not known yet, and not to be guessed at: whether Orion wants the old address kept.
What it asks
Sentinel is asking Athena, urgently, to hold the page until the link is fixed or removed. What should come back: hold or ship, as of the end of the day.
The shorthand
Packets can carry a few symbols to save space. The decoder always expands them, because a symbol the receiver has to guess at is worse than the words it replaced. Symbols are accents; the words carry the meaning.
| Symbol | Reads as |
|---|---|
| → | hands off to, or leads to (also typed as ->) |
| ✓ | checked and passed |
| ✗ | checked and failed |
| ? | open question |
| ! | urgent |
| ≈ | roughly, not exact (also typed as ~) |
| ∴ | therefore, marking an inference |
| ⟂ | conflicts with |
| #name | refers to a named item |
| @time | a time anchor: as of then |