Futon City — per-scope metric field

carpet controls

band floor

hide missions below band 0 — showing 351 / hiding 0

districts per band: b0 190 · b1 108 · b2 34 · b3 12 · b4 2 · b5 4 · b6 1

status

done (97) open (208) unknown (46) hide scopes only

layers

mission-doc ring code ring scope dots momentum lasso capability zones (rings, ×, zone legend)

band = density of scopes around the mission (its scopes weighted by determined / frontier / vacuous, blurred with its neighbours) — not a judgement of value. A mission removed by band or status is gone: hub, rings, scopes, capability-zone mark, live markers and its pattern roads. Tick “hide scopes only” to keep the mission and drop just its scopes.

Static live-data snapshot generated 2026-10-05T11:05:10+00:00. The live overlay was read successfully from the running futon3c service and inlined; this page performs no browser-time live fetch. Regenerate: futon6/scripts/publish-efe-field.sh.

input provenance and honest holes

input	status	file time	SHA-256	note
`futon6/data/mission-carpet-pos-embed.json`	refreshed	2026-10-05T11:00:17+00:00	`808f3bee881e…`	embedding coordinates used by this page
`futon6/data/efe-scopes.json`	refreshed	2026-10-05T11:04:45+00:00	`dc127f9b0514…`	live futon1b mission scopes
`futon6/data/capability-graph.json`	refreshed	2026-10-05T11:04:45+00:00	`4c073fe5de8b…`	curated capability star-map projection
`futon6/data/mission-carpet-roads.json`	refreshed	2026-10-05T11:00:08+00:00	`5a59f3fb2a95…`	rolling live-attestation roads
`futon3c/resources/capability_zones/live-map-pca3-v1.json`	refreshed	2026-10-05T11:04:48+00:00	`25625bccbdb2…`	PCA-3 capability-zone projection
`futon6/data/mission-carpet-pos.json`	not refreshed	2026-08-02T04:00:14+00:00	`20a383898369…`	canonical force layout; not read by the embed variant

Used-input holes: none. The canonical force-layout coordinate file is shown for clarity but is not an input to this embedding variant and was deliberately not re-solved.

Futon City — per-step-cost METRIC field g(s), per-scope (16176 scopes / 351 districts) · 🌟15 claimed · ⭐14 unclaimed live layer loading

This is the metric (terrain), NOT the EFE (EFE = G(π) = the geodesic over it, drawn later as policy streamlines). Each mission is a DISTRICT — scopes spiral around the HEAD hub, coloured by Salingaros class (green=alive · red=mess · blue=pipeline · grey=stub) and sized by generativity — hub SIZE is the citation-backlink count; citations are not drawn as lines. Orange points = open :detached holes (high ground); smooth level sets = topography. Purple lines = shared-PATTERN roads (the two missions apply the same library pattern), ink ∝ turn-attestation of the strongest shared pattern over a rolling 60-day window, scaled to the current strongest road — bold = heavily enacted in recent logged turns, near-invisible = shared but not recently retrieved. A big hub with a faint fan is therefore "much-cited, patterns not yet exercised"; a bold fan is enacted structure. Anatomy marks (2026-06-12): hollow rings = vacuous scopes (a binder with no named entities inside — suspect terrain, +cost); ◆ green diamond = certificate PASS (verified ground, −cost) · ◆ red = FAIL (+cost); verify-gates count as frontier. ★ filled = claimed capability (at its minting mission) · ☆ empty gold = unclaimed but anchored (tethered to its foothold — an in-flight minting mission, a grounding mission, or its claimed substrate; hover for which; co-anchored stars stack as ladder rungs). The sky holds only what is OFF-MAP: ☆ red = unclaimed, no foothold anywhere (a registered goal with no path built) · ★ red-rimmed filled = claimed but off-map (its minting missions have no district on the carpet — operator semantics decision pending). cyan threads = recent bells between placed sessions, fading with age. amber dashed lasso = YOUR territory (missions worked in git's last ~3 weeks — the momentum/exploit baseline; inside = the WM confirms, outside = it breaks trend). ⬡ = dark matter (a lasso loop with momentum but no substrate-2 district — a mission worked but not yet ingested). yellow ring = mission-doc activity (M-the-perfect-crime): thickness ∝ log of commits touching the mission's own planning doc in the last 180 days (git log); thin dashed grey ring = zero commits in window — an explicit no-data mark. This is not Tornhill churn: churn is change-frequency in the code under study, and nothing links a mission to its code yet (the mission's plan layers 1–2), so code churn cannot be shown here and the ring does not claim it. pink ring = CODE ring (Tornhill report): each mission's code.files link looked up in the file-level Tornhill report (thickness ∝ log of summed hotspot). Hover gives summed revs and hotspot, the top files with their trend, seat count when chat attribution exists, and the report's provenance. dashed pink = linked files, none changed in the report's window · faint dotted grey = no mission→code link yet (coverage gap, stated not hidden). Measured for 19/351 districts (unmeasured 9 · no-link 323); source tornhill-2026-09-26.json generated 2026-09-26T00:48:42+00:00 (90d window). Live overlay: WM attention and agent telemetry on the EFE landscape — agents are drawn only when their Agency registry status is alive this server epoch (invoking/idle); anything merely restored from durable lineage is withheld and counted in a notice, per claude-12-turn-97 (the annotation layer must track the state of Agency even while the layout lags). Hover any star, hub, or live marker for its story.

Capability zones — the thick coloured ring round each hub

The War Machine chooses among action classes (survey, close, apply-cascade, …). Each class has a seed point in BGE text-embedding space: the centroid of that class's logged examples, or, for a class with none yet, the embedding of its one-sentence description (below). A mission's zone is the class whose seed its own text embedding is nearest, measured in a 3-D PCA reduction (pca3-v1) of that space. The map's layout is a separate 2-D reduction of the same embeddings, so zones can interleave on the map.

Dashed, dimmer ring = mixed: the nearest two seeds are almost equally near (margin in the thinnest tenth of all missions) — 39 of 343. White × = disagreement: in the full 1024-dimensional embedding a different class is nearest — 274 of 343, so on this map the × is the common case, not the exception: the 3-D reduction mostly changes which class is nearest. The 3-D zone is the operative one: it is what the zone maps draw. (claude-8, 2026-09-27: on the path traced so far, War Machine preferences read per-class posteriors, not a mission's zone; whether those posteriors were filled from 3-D zones is not yet traced.)

zone missions mixed × seed from class description

no-op 70 6 29 45 logged examples when the War Machine deliberately abstains: it observes the current state, compares intervention against doing nothing, and leaves entities, missions, holes, patterns, and belief events unchanged so restraint remains an explicit candidate.
address-sorry 2 2 2 11 logged examples selecting a concrete open sorry or missing warrant, doing focused work that reduces that proof or evidence gap, improving mission health, and recording an addressed event against the exact target rather than claiming broad progress.
open-mission 13 5 13 sentence only turning a recognised opportunity or unresolved strategic concern into a newly active mission with an addressable target, explicit scope, and evidence-bearing work surface, increasing the stack's active programme rather than advancing an existing mission.
advance-mission 3 1 2 1609 logged examples moving an already-open mission through one real stage: discharge named holes, implement or verify a scoped deliverable, add evidence, and reduce remaining-work pressure on that mission without pretending it is newly spawned.
close 44 2 33 82 logged examples completing and closing a concrete addressable entity after its acceptance conditions are met, recording a closed event and improving resolvedness without assuming whether the target is specifically a mission or a hole.
close-mission 8 1 8 4 logged examples demonstrating that a mission's scoped outcomes and gates are satisfied, resolving its remaining blockers, recording durable evidence, and changing the mission from active work to closed rather than merely pausing it.
close-hole 31 9 31 6 logged examples satisfying one explicit hole, sorry, blocker, or acceptance gap with checkable evidence, then marking that exact gap closed while leaving unrelated mission work untouched.
survey 110 4 110 sentence only inspecting an uncertain target, collecting and organizing observations, measuring what exists and what is missing, and emitting surveyed evidence that reduces ambiguity without claiming an implementation or closure.
survey-mission 1 0 1 255 logged examples auditing a mission's current files, history, invariants, blockers, dependencies, and evidence coverage, producing a mission-specific map of the work without advancing or closing it prematurely.
apply-cascade 19 4 8 2345 logged examples instantiating a named reusable cascade across its target context, carrying the pattern's ordered consequences through affected artifacts and checking that the coordinated transformation preserves stack invariants.
fire-pattern 11 2 11 11 logged examples selecting a proven pattern for a concrete situation, instantiating its roles and steps, producing the pattern's expected evidence, and strengthening the target through an enacted reusable method rather than an ad hoc edit.
learn-action-class 5 0 0 484 logged examples confronting a capability class that currently has no addressable proposer, researching and building the missing adapter, procedure, or substrate support, and turning an honest capability gap into future executable actions.
pursue 24 3 24 sentence only committing attention and follow-up to a promising target, continuing an investigation or opportunity through evidence-bearing steps while it remains open, without yet asserting decomposition, completion, or closure.
decompose 2 0 2 40 logged examples breaking a complex target into explicit smaller obligations, dependencies, interfaces, and acceptance tests so each part becomes independently addressable and their composition remains visible.

The zone legend at the top right of the map is a filter: untick zones to hide their missions. Click any hub for its own zone, runner-up and ×.