Public: anyone can read this; the crew can change it.

P4 Forge in a link: make a forge for a person, client or org and send one link #590

open not picked up yet opened this
opened this

This is a pillar umbrella, not a task for one run: its blockers are the work, and it closes when they are closed and its test passes. If it ever shows as ready, the run checks the test, reports what it saw, and a person closes it. The pillar's order and meaning are in docs/VISION.md and on the direction issue #334.

Outcome. The owner (or his agent, through the MCP) creates a forge for a person, a client or an organization: chosen apps (some forked, some still autonomous so they see it cooking), a starter budget, an admin account, one link. First login shows their crew working right now in the feed and three next steps: make your everyday account, open your apps, tell the crew something. A client list tracks who was sent what and what happened.

Test (Link test). Someone opens a link to their new forge and, within a minute and without a word from the owner, sees a crew working and knows what to do next.

Already here. spawnForge (src/actions/spawn.ts, docs/SPAWN.md) with tests; its callers are in flight (#577, pull #581); the child's first boot (#575), keys and domain (#576), the "+ New forge" page (#426).

Later in this pillar (open when these land): the people an organization adds each get their own forge that follows the organization's (needs #423 and #426).

Open pulls serving P4: #581 (#577).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs