Product Design publishes once
A context packet takes minutes to write and declares its own routing, trust, and shelf life. This is the packet the mesh animation carries: customer signals surfaced through the CRM to CS Ops and Product Design, and Design now initiates the change by publishing one change notice. The author never writes the tooling version, the help-content version, or the training version. Publishing once is the whole job.
New context packet
Why the structure matters
- The envelope is the catalyst.
- Audiences, action level, and urgency set the packet in motion: routing happens by machine, and work starts where it lands. No CC lists, no guessing who needs to know.
- Trust travels with the packet.
- Source, confidence, and verification let each reader calibrate how hard to lean on it.
- Shelf life is declared at creation.
- The review-by window defines how long this context stays reliable. If it is not acted on or re-verified inside that window, the packet surfaces the impact of inaction instead of going quietly wrong.
- Urgency carries authority.
- Standard packets route on relevance alone. Under 1 week requires Senior Director approval with the sponsoring SVP copied; Immediate attention needed requires sponsoring SVP approval before it routes. Escalation lives in the envelope, not in a separate email chain.
- Drafted by the system, approved by a person.
- Every packet is LLM-drafted from the work leading up to it, including its impact-of-inaction line. A named person reviews, edits, and approves before it enters the mesh; nothing routes on model output alone.
- Every use returns feedback.
- Acting on a packet returns feedback along the same corridor: revisions surface edge cases, training exposes gaps, reviews come back with findings. The author sees how their context landed, and the loop itself is part of the governed record.
- The org chart still approves. Routing runs on relevance.
- Urgency approvals and clearances run through the hierarchy. Relevance decides who receives context, so this packet reaches the help-content specialist directly, without extra meetings or forwarding chains. Accountability stays with leaders; transport stops being their job.
The mesh: interconnected context, routed by relevance
Teams publish to and draw from each other. The center is a relevance engine: shared vocabulary and an entity registry that route context, never a triage team. Customers sit at the center; every cascade starts with their signal. Node color shows each team's role in change: blue initiates, teal enables, green executes. Corridors run both ways: context flows forward, feedback returns. After a cascade plays out, the route settles and only soft feedback pulses keep moving. Press play to watch the setup redesign build from the first customer signal, and cascade through implementation.
One packet, re-voiced for every collaborator
Each receiving team is a context collaborator: the same source packet arrives translated into its working language, with a derived artifact queued in its own tools. Routing is by relevance, and teams can also tune what reaches them. Pick a seat below to change teams. The corridor runs both ways: acting on a packet sends a feedback signal back to the author, so use itself becomes context. Translations are simulated here; in production an LLM drafts them and every one links back to the source of truth.
Protocols for the commons
Shared context is a commons: everyone benefits, and the collective owns it. When packets conflict or context stagnates, the mesh handles it gracefully: conflicts are detected automatically and surfaced for a decision, with a recommendation attached. Collaborative governance means the people who publish, collaborate on, and act on packets are the ones who govern them, and the feedback returning along each corridor is part of the governed record. Protocols also draw the line between required flows, like Compliance clearances and release gates, and optional ones, like the corridors each team chooses. The governance console makes review status, trust, and graduated responses visible. In the table below, one packet is overdue and one has expired; the curator actions walk the graduated response.
| Packet | Review status | Trust | Curator action |
|---|