The outcome you are walking toward
A working map of six integration families that already have honest public leaves — enough outline to brief IT, pick the right starting docs, and know what still waits on a site survey. This page deepens the family map with actionable steps. It still does not claim that every POS, PMS, access, or equipment recipe is published.
What this page is (and is not)
- Is: six pattern outlines that point at real Triangle auth, Mesh / Synapse, webhooks & events, edge offline, agent authority, data fabric, and STORE Solution kit composition.
- Is not: a “coming soon” hub that pretends named-vendor coverage it does not have.
- Is not: vendor certification badges, invented availability guarantees, or partner SDK marketing.
- Is not: a rewrite of the STORE Solution page — kit BOMs live under `/solutions/store`.
- Is not: a claim that a live agent simulation environment ships on this site (that tooling is internal enablement when it exists).
Deal-specific boundary tables and named-system recipes are shared through a diligence briefing or scheduled briefing. Until then, treat category rows (POS, access, equipment, PMS) as OPEN placeholders.
Pattern family 1 — Identity / Triangle auth
When to use: a stakeholder asks how sign-on, sessions, and brand-scoped grants work across surfaces.
Outline
- Establish one credential path — start at Triangle: secure sign-on.
- Confirm how sessions and tokens are modeled — token model.
- Check brand isolation for data and grants — per-brand data isolation and identity overview.
- Walk a security review path — security review walkthrough.
Canonical leaves: /docs/triangle-auth · /docs/triangle-token-model · /docs/triangle-identity · /docs/per-brand-data-isolation · /guides/security-review
Honesty: no invented SSO partner certifications. Engagement-specific grant matrices stay briefing / NDA.
Pattern family 2 — Event / Mesh–Synapse + webhooks
When to use: builders need discovery, priority signaling, or outbound event integration without inventing a second bus.
Outline
- Orient on interconnect health and discovery — Mesh.
- Orient on priority signaling — Synapse.
- Contract outbound delivery — webhooks & the event substrate (at-least-once delivery; consumer idempotency is the other half of the contract).
- Stay inside builder limits — integration boundaries.
Canonical leaves: /platform/mesh · /platform/synapse · /docs/webhooks-events · /docs/integration-boundaries
Honesty: no invented uptime numbers, partner badges, or bare once-only delivery claims. Topic / endpoint matrices for a named site stay OPEN until the survey fills them.
Pattern family 3 — Edge offline resilience
When to use: IT or counsel asks what a location does when the uplink is gone.
Outline
- Read the offline behavior contract — edge offline resilience (MUST / MAY / FORBIDDEN).
- Separate public conformance language from internal attestations — conformance LEVEL.
- Tie offline actions back to evidence — audit trail & evidence.
Canonical leaves: /guides/edge-runtime-offline-resilience · /guides/conformance-certification · /docs/audit-trail-evidence
Honesty: public surfaces use LEVEL language only. Per-capability offline tables for a pilot site stay engagement templates.
Pattern family 4 — Agent authority boundaries
When to use: counsel or ops needs a defensible answer to “what may this agent do?”
Outline
- Treat capabilities as signed data — authority model.
- Confirm governed boundaries — governed agent boundaries.
- Check high-impact approval gates — approval gates.
- Reconstruct one consequential action from evidence — audit trail · audit trail review.
Canonical leaves: /guides/agent-authority-model · /docs/governed-agent-boundaries · /docs/agent-approval-gates · /docs/audit-trail-evidence · /guides/audit-trail-review
Honesty: observation / shadow / canary modes are design concepts — do not treat a public marketing page as proof a live simulation harness exists. Action-class / gate / owner matrices for a deal stay briefing-supplied.
Pattern family 5 — Data fabric
When to use: stakeholders want shared operating record before dashboards or one-off extracts.
Outline
- Orient on authority, identity, lineage, and freshness — data fabric orientation.
- Read why the fabric precedes dashboards — data fabric before dashboard.
- Check isolation mechanics — RLS isolation.
Canonical leaves: /docs/data-fabric-orientation · /blog/data-fabric-before-dashboard · /docs/rls-isolation-mechanics
Honesty: the fabric is not a lake of unowned copies. Source / authority / freshness matrices for a named estate stay OPEN until the survey.
Pattern family 6 — Kit / BOM composition (STORE Solution)
When to use: deployment or IT asks what physical kit composition looks like for a location class.
Outline
- Start from the canonical Solution surface — MCV.STORE.
- Read the layer model so kit pieces sit in the right stack — layer model.
- Pull the vertical hardware playbook that matches the site — Helix, Ember, Domain, Scaffold.
Canonical leaves: /solutions/store · /docs/layer-model · hardware playbooks above
Honesty: Capital and Law stay agent-only — no physical-kit pattern pages for those verticals. Do not invent public inventory counts or unit prices here; commerce posture lives on the STORE Solution page under its own pack.
What we deliberately leave blank here
Category rows for POS, access, equipment, PMS, inventory / RFID, and similar systems appear as engagement templates in the internal pattern library — not as published vendor recipes. If a named recipe is not linked above, it is OPEN, not shipped.
Who this page is for
IT and systems stakeholders in a multi-stakeholder deal — the same audience as the IT row on who we brief by role. Operators evaluating pilots should still start from deployment phases and the buyer journey.
Requesting a deeper integrator pack
Ask for the engagement boundary table and any gated depth that matches your site survey on Request Access, or start from the diligence reading path. We will not invent availability guarantees or certification theater to fill empty cells.