The pack · public release preview

/api — the Stream Engineer

A staged build of one income asset, run by an agent team in your own terminal and repo. It ranks the archetypes against your real inventory, wires the surfaces you already own, scaffolds the engine, and holds the work to your own stop conditions.

The system · /api · release preview

Advice disappears. Decision artifacts compound.

/api is the agent-side execution system: eliminate bad stream fits, map the surfaces you already own, specify the engine, install a bounded maintenance loop, and audit it. Every stage writes a reviewable artifact into your repo. The human keeps authority over claims, money, and publication.

public release gate

The pack is built. Public installation is paused while the free open core is separated from paid delivery. No dead install command, fake access, or private-repository 404 is presented as a launch.

Inspect the five stages Join release access

decision-record — local preview

Atlas ratings verified 2026-07-11 · quarterly review cycle

/api streams

Reading inventory… newsletter (2.3k) · site (41 evergreen pages) · 12 honest hrs/mo

Eliminated 9 of 12 archetypes — labor floor or latency exceeds budget.

Selected: 03 digital product line

Maintenance floor: 5–10 hrs/mo

Kill criterion: first cleared economic event by Oct 15 — or sunset.

→ wrote streams/00-stream-selection.md

/api connect

Mapping surfaces… newsletter carries · site converts · X feeds.

Nothing gets built that an owned surface already does.

→ wrote streams/01-surface-map.md

/api engine

The five stages

Every stage ends in a written artifact.

/api streamsRanks the 12 stream archetypes against your surfaces, skills, and honest hours — eliminations cited from the atlas, kill criterion mandatory before anything is written.streams/00-stream-selection.md

/api connectMaps your existing website, socials, and newsletter into the stream plan — what feeds, what carries, what gets built new. Nothing gets built that an owned surface already does.streams/01-surface-map.md

/api engineScaffolds the machine: registry, templates, integrity gates, pipeline config. Registry first, always — automating generation before the gates exist just industrializes error.streams/02-engine-spec.md

/api loopInstalls the recurring automation — idempotent, capped, observable, gated. No loop earns direct publish rights, ever.streams/03-loops.md

/api auditFreshness and integrity pass on a running stream: stale facts, dead links, disclosure presence, program-term drift.streams/audits/YYYY-MM.md

Doctrine, non-negotiable: no income promises — labor floors published on every stream. One stream at a time. Every stream gets a kill criterion at selection. Honest costs on everything. Disclosure by default. If it lives only in a chat, it doesn't exist.

The team inside

Four specialists, one quality floor.

stream-engineer

Lead — ranks the 12 archetypes against your real inventory, designs the chosen machine, owns the honest economics and the kill criterion.

content-machine

Pipeline builder — scaffolds registries, templates, and gates; generates artifacts with evidence labels from registry facts. Never publishes.

seo-editor

Search + GEO — optimizes for organic search and LLM citation while keeping every claim sourced and dated. Owns freshness discipline.

syndicator

Distribution loops — cuts canonical long-form into platform-native derivatives that link back home. One canonical, many cuts.

Runtime posture

Markdown intelligence. Runtime adapters.

The richest path is a Claude Code plugin with specialist-agent routing and scheduled loops. The core instructions and schemas stay in readable files so the method can be adapted to Codex, Gemini CLI, Cursor, and OpenCode. Public install instructions remain withheld until the open-core release passes its visibility and paid-delivery gate.

Request release access Run the viability audit first

Get the /api public-release note

One message when the open core is public and the install path works. Product access is kept separate from the editorial Brief.

Online intake is not connected on this deployment. No address is collected; this access note will reopen when a verified delivery path is live.