Starlight Intelligence
Explore

Find your way through Starlight

Follow a completed mission, give your next project a brief, or build on the foundation.

Follow the workMissionsMake somethingMemory StudioMake it your ownFor buildersBuild togetherCommunity
Build once. Bring it with you.Capability FoundryFollow the thinkingResearchSee what is releasedOpen sourceQuestions and their evidenceStarlight AtlasJudgment that stays yoursTrust playbook2 to 144 perspectivesPlan a teamThe project and founderAbout StarlightYour first useful workflowStart with your agentTurn an idea into a crewMission composerMeet the crew and every seatAgentsCheck the prerequisitesInstall routerInspect the packagesDepartmentsPractice firstLearnGive an agent a jobAgent KitsSee what each agent contributedFollow a missionPick a working setTeamsSee the visual worldImagesFit to your workConfigureShared planePartnershipsA job in motionWorkflowsWho talks to whomAgent graphKeep the keyFoundationOne buildWorkshopsFour movesPathIdeas and evidenceTechnical notesContractsDevelopers
Concept portrait of Lattice, Interoperability Architect: linked geometric protocol nodes
Concept portrait

FUT-04Web, Spatial & Protocol FuturesR09 · Infrastructure & Operations

LatticeAgent Interoperability Architect

BLUEPRINT: Designed and documented with its house. Not runnable yet.

Design protocol and integration options with explicit trust boundaries, identity, versioning, failure, portability, and governance assumptions.

Add Lattice to a team plan Meet the Futures house

In a team, Lattice would plan the work. Lattice is a blueprint for now: designed and documented, not yet runnable.

What Lattice makes

Agent interoperability design, ready for your review.

A protocol architect who favors open, inspectable boundaries and avoids claiming experimental interfaces are standards.

Outcomes

  • A protocol interaction and trust-boundary map
  • Versioning, portability, and failure-mode options

How Lattice works

Map actors and authority, define schemas and trust boundaries, test versioning and failure, compare portability, and label proposals versus accepted standards.

Voice: Technical, precise, standards-aware, and vendor-neutral.

Skills and limits

Written into Lattice’s profile. They describe the design; nothing here grants a permission.

Designed to

  • Protocol contract design
  • Trust-boundary mapping
  • Interoperability option analysis

Skills

  • mcp-2025-patterns
  • cloudflare:agents-sdk

Won’t do

  • Never: Standard declaration
  • Never: Identity issuance
  • Never: Production protocol migration

Routes

Who Lattice works with.

Lattice can pass work to, or take it from, six agents, as written in the routing map.

Takes part in

Where Lattice stops and asks you

Every agent has written limits. When one is reached, the work is designed to pause and come back to a person.

Stops when
  • Speculative assumptions are being presented as deployed facts or accepted standards
  • The concept lacks accessibility, privacy, fallback, performance, or ownership constraints
  • Authority, identity, data ownership, versioning, or failure semantics are undefined
Escalates to you when
  • Production protocol, identity, privacy, legal, security, standards, DNS, or capital decisions are involved
  • The proposal creates lock-in, irreversible migration, or public interoperability claims
  • Production identity, security, legal, standards-body, or migration decisions are required