Applied intelligence systems · Life OS + Swarm Factory

Your agents stop forgetting. Your system starts compounding.

Design the memory, authority, evidence, and evaluation layer around one workflow that already matters — then run portable swarms across the CLIs you already use. You hold the keys.

Design your system Inspect a worked receipt

Substrate: SIP + Starlight Kernel
Authority: Human-gated
Evidence: Receipts before claims

Worked example · not a client result

Weekly product evidence brief

promotion held

Scope

Name one recurring workflow and the decision it must support.

Ground

Attach sources, ownership, boundaries, and failure evidence.

Route

Assign specialist work while preserving a visible human authority point.

Verify

Require receipts, tests, and a reversible release decision.

Remember

Commit the result, context, refusals, and unresolved forks to durable memory.

Owner · product leadNext action · collect run 02Evidence score · 1 / 4

01 / Operating shift

Most teams bolt agents onto chat.

Starlight is the intelligence system underneath the fleet: shared memory, organization, evals, and governance — portable across tools, orchestrated by Queen, constrained by charter.

Prompt hoping → Bounded route

Specialists run inside declared authority, not open-ended vibes.

Session amnesia → Durable memory

The next agent reads the same decisions, gates, and forks.

Autonomy theater → Evidence gate

Promotion waits on receipts. Humans keep the irreversible keys.

03 / Blueprint studio

Design one system. Download the brief.

Browser-local only. Nothing is uploaded. You leave with an implementation-ready intelligence-system brief: memory, authority, gates, refusals, eval bar, and next slice.

Workflow nameOne recurring process

Owner roleHuman decision rightsEvidence runs requiredPromotion bar

Decision this workflow supportsSourcesComma or line separated

Agent mayAgent may notHuman-only actions

Private memoryNever route to agents by defaultEvaluation bar

Stays on this device. Open substrate and protocol live at starlightintelligence.org.

Live brief · browser local

Weekly product evidence brief

Evidence0/4

OwnerProduct lead

Gates blockednone

Promotionheld

Scope
Whether the weekly product claim set is ready to publish
Ground
Ground every run in: Issue tracker; shipped PR list; preview URLs; prior brief receipt.
Route
Specialists may: Collect sources; draft brief structure; flag missing evidence; score completeness. Visible authority point remains the owner.
Verify
Require receipts and 3 comparable run(s). Promotion stays reversible until the owner decides.
Remember
Commit result, context, refusals, and unresolved forks to durable memory the whole fleet can read.

Gates

open
Named human owner
Product lead holds final decision rights
open
Source packet
4 source class(es) declared
required
Evidence bar
3 comparable run(s) required before promotion
required
Human decision
Promotion, publish, merge, pay, and external send remain human-gated

Refusals

Publish
Outside declared agent authority for this workflow
change pricing
Outside declared agent authority for this workflow
invent metrics
Outside declared agent authority for this workflow
approve claims
Outside declared agent authority for this workflow

Next implementation slice

Implement the smallest slice that produces one complete receipt for “Weekly product evidence brief” using only declared agent authority.

04 / Mission Control

See the system without surrendering the keys.

Plans, agent roster, swarm lanes, human gates, refusals, and evidence scores — one graspable surface. This panel is a synthetic product demo, not a live estate feed. Private operator observatories stay private.

Demonstration · synthetic tenant data

Founder fleet · sample workspace

demonot live estate

Agent rosterAuthority map

Starlight Queen
Admit · reduce · handoff
orchestration
Researcher
Draft only
web · docs
Implementer
Draft PR
repo · tests
Checker
Read-only verdict
diff · eval
Human owner
Irreversible gates
merge · publish · pay

Active lanesSwarm runs

L1Memory modulescore 2/4
Memory steward · verifying
Two-CLI shared vault smoke in progress
L2Code / PR swarm packscore 1/4
Swarm architect · drafting
Pack schema + sample receipt
L3Blueprint productscore 3/4
Frontend Queen · ready-for-review
Browser-local brief generator

Human gatesCharter-visible refusals

blocked
Promotion
Evidence bar is 3 runs · 1 complete receipt on file
blocked
External send
No approved outbound packet
open
Draft PR
Inside implementer authority · no force-push

Memory health

Shared vaultsconnected

Contradictions0 open

Private planelocal only

Queen reduces evidence · Luminor seats advise on long horizon · humans decideExportable · fail closed · no unattended irreversible actions

05 / What compounds

Not more agents. A better kernel.

Super-capable agent teams matter only when the substrate keeps human meaning, memory, and refusal intact as capability rises.

Shared memory

One vault layer across Claude, Cursor, Codex, and the rest of the fleet — so decisions compound instead of resetting.

Organization

Named roles, plans, domains, and pack shapes. Swarms stop being chat theater and become operable systems.

Evals & receipts

Evidence scores, promotion bars, and stop conditions. Claims stay declared, observed, or verified — never upgraded by wording.

Governance

Benevolence charter in the product: refusals visible, irreversible actions human-gated, export and leave always possible.

06 / Portfolio

Three surfaces. One clear job for each.

The applied product lives here. The protocol remains open at .org. Learning belongs at Academy when cohorts open.

.aiApplied systemsBlueprint, packs, Mission Control product .orgProtocol and researchSIP, open substrate, public trust SIPOpen kernelFile contract, attestation, sovereignty clause

Final action

Leave with a system brief, not a pitch deck.

Generate the brief locally. Keep ownership. When packs ship, install them into the tools you already run.

Create and download the brief Visual lab