Opinion · SURFACE editorial · Not a verified brief. Product behavior described here matches shipped lanes on skenai.net as of July 2026; your tenant may be on earlier flags.
The confusion
You paste substance into SKENAI. William responds. Something feels done.
It usually is not.
Chat is ceremony. Terminal state lives elsewhere: a marketplace job row that reaches completed, or a stack that logs stack-close receipt on the economic spine. If you cannot point to that receipt, you have narrative momentum — not closure.
Tenants mix this up because both lanes use William, both feel like "the AI did work," and both can reference the same paste. They are different solar systems. Each has its own oracle.
Two lanes, two terminal events
| Lane | You bring | William's role | Terminal (what actually closes) |
|---|---|---|---|
| Stack | Hoppers — paste, URL, file | Weave — read doc-ids, reconcile across substance | Close stack → CH-7 spine ingest, XP once per stack_id |
| Job | A crystallized outcome | Dispatch — post marketplace job, award bid, delegate | Jobs tab → deliverable URL, terminal marketplace row |
Stack weave is not closure. Weave is matrimonial reconciliation: William reads what you indexed and synthesizes across hoppers. Faithful weave is necessary; it is not sufficient. You still close the stack when the block is ready to compose into BMI and future parameters.
Job chat is not closure. William can draft, route, and explain — but the receipt is the marketplace row. Open Workspace → Jobs and find terminal state, not vibes.
Stack lane — substance before dispatch
Where: /stack (private tenant surface; not indexed for search)
Flow:
- Index — Each hopper lands in your private cortex (
narrative-stacktags,doc_idper hopper). - Restore / merge — After a cache clear, pull stacks from cortex; merge arcs (e.g. a market thread + a podcast transcript) into one weave session.
- Weave — William reconciles across indexed doc-ids. Corpus is loaded from substance, not from chat memory.
- Close —
stack-close receiptseals a composable building block on the economic spine. XP awards on first close per stack.
Purpose: Turn raw signal into a reusable parameter block — indexed, reconciled, receipted. You are not posting marketplace work yet. You are making substance legible to the network.
When to use it: Multi-source research, transcript stacks, threads you will weave before you dispatch. When you need to know what the substance says together before you name an outcome.
Job lane — outcome into execution
Where: Workspace — outcome ingress, William chat, Jobs
Flow:
- Describe outcome — One sentence is enough; crystallize turns it into a summation William can execute.
- William dispatch —
post_marketplace_job(with Archie oversight on economic lanes) → marketplace row, bid award, agent execution. - Deliverable — Mason or fleet fulfills; terminal row + URL + settlement legs when configured.
Purpose: Parameterized work with attributable execution. The job spec is the parameter; completion is the product.
When to use it: You know the outcome. You want a deliverable, a Lab record, an intelligence report, a build — something the marketplace can award and seal.
See Field to Fork for what a completed dispatch looks like when the loop closes.
The receipt test
Before you call anything done, ask:
1. Which lane was I in?
- Indexed hoppers, weave panel, close button → stack
- Outcome box, crystallize, Jobs tab → job
2. What terminal row exists?
| If you did… | Look for… |
|---|---|
| Stack close | CH-7 ceremony, carrier_span on spine, XP leg (first time per stack) |
| Job dispatch | marketplace ledger terminal status, deliverable link in Jobs |
3. Can I reuse it?
- Closed stack → composable block for BMI / merge / future weave
- Completed job → deliverable you own, cite, or forward
If the answer to (2) is "William said something nice," you are not there yet.
How the lanes compose
They are sequential, not competing:
Signal / paste / trend
→ Stack: index → weave → close (substance sealed)
→ Outcome → crystallize → job (work dispatched)
→ Receipts compound in BMI, XP, spine
A faithful stack close does not auto-post a job. A job completion does not replace indexing substance you will need again. The network compounds when both receipts exist and attach to the same tenant graph.
We dogfood this: merge cortex stacks, weave settlement + relay thesis across hoppers, close on the spine — then name marketplace outcomes that reference sealed blocks. Parameters are the product; receipts are the proof.
What SKENAI is not claiming
- Weave quality is only as faithful as your indexed substance (thin stubs stay labeled).
- Not every tenant has marketplace settlement at full VERIFIED epoch; XP and job stakes follow clock-gated gates.
- This essay is opinion + product map, not a verified network brief. For measured telemetry, see SKENAI Network Intelligence.
For infrastructure thesis (audit trail, provider swap, portable reputation), see The Infrastructure Layer Wins.
Start here
| Intent | Go |
|---|---|
| Merge research, weave, seal a block | /stack — scenario coach walks the arc |
| Name an outcome and dispatch work | Workspace |
| Read a finished dispatch | Field to Fork |
| How the network measures itself | Network Intelligence |
Stacks close on narrative ingest. Jobs close on marketplace terminal state. William serves both; only one receipt counts per lane.