app.canopi.live/breaking-out
Meta-layer canvas
Preview layout below mirrors a host page + meta-layer sidebar: interact with primitives on the left, fill design blocks in the content column. Open Learn for boundary objects and vocabulary. Display mode hides the sidebar tools for a cleaner stakeholder view.
NEXT_PUBLIC_WEB3AUTH_CLIENT_ID (same as gov-hub) to enable sign-in. You can still edit locally; work is saved in this browser.The preview frame uses a meta-layer sidebar and a host content column. Use the interactive primitive demo in the sidebar, then map terms to each block in the page column.
Boundary objects
A boundary object sits between communities or roles that describe the world differently. It stays stable enough to coordinate action and loose enough that each group can read their own meaning into it—maps, specimens, shared forms, or a agreed label on ambiguous terrain.
On this canvas, each block you fill is a boundary object: your audience sketch, host patterns, anchor notes, and surface specs are artifacts people can align around without collapsing every discipline into one jargon.
Boundary infrastructure · Canopi
Boundary infrastructure is what holds those objects in practice: identities, URLs, permissions, registries, and shared surfaces that let different worlds attach to the same place without merging into a single silo.
Canopi aims to be that kind of infrastructure on the web—a meta-layer where presence, context anchors, tabs, sidebars, and smart tags translate across sites and participants. Your design here says how your layer uses that infrastructure on specific hosts.
Meta-layer primitives → sections on this page
Learn the vocabulary once; use it consistently in specs and when mapping to real tab apps and smart tags in Canopi.
- AudienceWho shares the boundary object and what job they are doing.
- Host pagesWhere the infrastructure attaches (URLs / patterns).
- Context anchorsMeaning tied to passages or elements—not only the whole viewport.
- Full-page momentsWhen the layer briefly owns the full surface for orientation or ritual.
- TabsWhether multi-document workflows need coordinated boundary objects across tabs.
- SidebarPersistent negotiated workspace—shared state next to the host page.
- Smart tagSmall boundary object on content (selection, hover, proximity)—high signal, low chrome.
- OverlaysTemporary shared focus; explicit enter/exit so boundaries stay legible.
- Context & dataWhat crosses boundaries (DOM, URL, APIs) and privacy stance.
Host page · content column
Audience, URLs, surfaces, and pitch live here as blocks inside the page — where participants focus while the layer assists from the side.
Identity & scope
Saved in this browser under anonymous