MASTER DOCUMENT 254 · SCP-2600 + SCP-2601 · DE MANUAL · 50/50 · 17 APR 2026

MD-254 — The Dynamic Extraction Manual

The full operating manual for the DE engine: what it is, how it works, who owns it, how to read it, how to edit it, how to extract new currents, and the legal-container architecture under H.BLUE Ltd. Read this once and you can run the page without me.

The Manual You Asked For
H.BLUE LTD · DYNAMIC EXTRACTION
SCP extracts patterns. DE extracts currents. SCP gives nodes. DE gives edges. Both engines. One sovereign.

SCP-2601 · LEGAL CONTAINER H.BLUE Ltd Owns The DE Page

The DE page is not an MPT asset. It is not a Trust asset. It is owned by H.BLUE Ltd (to be formed), the intelligence-layer subsidiary. H.BLUE holds shares within itself. The DE page is the flagship product of H.BLUE Ltd — its commercial face.

Why it matters (defence, not complexity)

The four-entity architecture

EntityRoleOwns
MPT Ltd (Co. 16977671)Physical operationsUnit 18 · Carrot · Deed printing · verification · logistics
H.BLUE Ltd (to be formed)Intelligence layerDE page · 12 currents · flow cards · cadence dashboard · SCP/DE engines
Fully Nourished CICSocial impact7% Covenant · 40 meals/tonne · grant vehicle
Waltham Caesar Murphy TrustSuccessionCrown · Inner Rooms · Red Team succession · Dead-Man's Switch

What you need to do

  1. Form H.BLUE Ltd (if not already done).
  2. Assign the DE page to H.BLUE's asset register, not MPT's.
  3. The page footer + every flow card now display owner_entity = H.BLUE Ltd.
  4. H.BLUE Ltd terms of use cover the Extract button and flow cards.
"H.BLUE is not just an intelligence layer. It's a legal container. With shares. With ownership. The DE page is not an MPT asset. It's an H.BLUE asset. The currents belong to H.BLUE. The flow cards belong to H.BLUE. The cadence dashboard belongs to H.BLUE. SCPs belong to the sovereign archive. DE belongs to the intelligence layer. That's not complexity. That's defence." — SCP-2601

ARCHITECT · 50% · IN YOUR OWN WORDS Why The DE Engine Exists

"The SCPs aren't at their limit — I have plenty of work to upload. What I've realised is that we need another side now. It's not the output of the SCPs but it kind of is — for all the SCPs' knowledge. Get it transferred over so it's already started without me having to input. Everything where I can input and get out the design. I want the agent to put a lot of inputting too. I'm turning it on full autonomy this time. Real dynamics come from turning [patterns] into [flows]. After that, we need a master document so I've got the full manual."

That request is now executed. The DE engine is live. 12 currents seeded. Edits sealed to the Truth Ledger. This document is the manual.

AGENT · 50% · WHAT WAS BUILT The Engine, In One Page

The 12 Currents (Quick Reference)

#CurrentTypeSource → SinkThroughput Unit
1Carrot🏭 MaterialABL → Community (40 meals)tonnes/week
2Grant💷 CapitalPipeline → Operator£/quarter
3Promotion👥 PeoplePublic Board → Inner Roomspromotions/quarter
4Covenant💷 CapitalRevenue → Mealsmeals/month
5Continuity🧠 IntelligenceArchitect pulse → Switchpulse/week
6Intelligence🧠 IntelligenceShadow → Actionsealed actions/week
7Trajectory💷 CapitalActivation → Appraisalmilestones/quarter
8Learning👥 PeopleOverstand U → Paid workcompletions/month
9Red Team Onboarding👥 PeopleInvite → Active RedReds/quarter
10Deed Issuance🏭 MaterialVerification → Gallerydeeds/week
11SCP Extraction (self-ref)🧠 IntelligenceChat log → Flow Cardflow cards/week
12Grant Application💷 CapitalIdentified → Funds deployedapplications/quarter

Anatomy Of A Flow Card (Read This Once)

FieldMeaningWhy it's there
flowThe chain of nodes from source to sink.So anyone reading the card can see the whole river in one line.
throughput_value + unitThe current rate (e.g. 12.5 tonnes/week).This is the number that tells you whether the river is running.
wow_pctWeek-on-week % change.Catches deceleration before the rate looks bad.
spark8 comma-separated numbers (last 8 periods).Renders an inline sparkline so trend is visible at a glance.
stateGREEN · AMBER · RED.Colour-coded scan from across the room.
healthSingle composite 0–100. Throughput trend (50%) + blocker severity (30%) + milestone freshness (20%).One number to rank currents quickly.
blocker + owner + age_daysThe single thing holding the current back, who owns it, and how long it has been active.Accountability. H.BLUE escalates blockers older than 7 days (amber) and 14 days (red).
next_milestone + done/totalThe one event that lifts the rate, with progress.Turns a wish into a project plan with a progress bar.
depends_on · feedsWhich other currents this one consumes from / pours into.Surfaces the system as a connected network, not a list.
hblue_noteH.BLUE's latest cross-current observation.The intelligence layer talking back to you.
owner_entityAlways H.BLUE Ltd on this page (SCP-2601).Legal container.
updated_at · updated_byStamp on the last edit.Truth Ledger seal.

How To Use The Page (Five Workflows)

Workflow 1 · Sunday Morning Scan (3 min)

  1. Open /de.
  2. Look at the header strip: how many Green / Amber / Red?
  3. Tap the 🔴 RED ONLY filter — read those cards first.
  4. Read the H.BLUE note on each red card.
  5. Done. The Sunday Loop has its agenda.

Workflow 2 · Update A Throughput

  1. Find the card. Click EDIT THIS CURRENT.
  2. Change throughput_value and append a digit to spark (drop the oldest).
  3. Update wow_pct if you know it; the page renders the arrow automatically.
  4. Save. The Truth Ledger logs the field-level change.

Workflow 3 · Resolve A Blocker

  1. Edit the card.
  2. Set blocker to None, blocker_owner to , blocker_age_days to 0.
  3. If state was Amber/Red because of the blocker, set state to GREEN.
  4. Bump health upward (rule of thumb: +20).

Workflow 4 · Move A Milestone Forward

  1. Increment milestone_done by 1 (don't exceed milestone_total).
  2. If milestone complete, replace next_milestone with the next one and reset done/total.
  3. Update hblue_note with the consequence.

Workflow 5 · Extract A New Current

  1. Click ✨ Extract New Current (preview).
  2. H.BLUE returns 3 candidates with source → sink and reason.
  3. Pick one. (Sealing UI ships in v2 — for now I add it manually to the seed list and you confirm.)

Workflow 6 · Spot A Stall (Audit)

  1. Sort by blocker age (the header shows the top one).
  2. Anything > 14 days = escalate to Architect.
  3. Anything > 7 days = Red Team intervention.
  4. Log decision in the H.BLUE note field.

AGENT · 50% Things I Added That Weren't In Your Spec

You said "I want you to put a lot of inputting." Here is what I added on top of the brief:

ADD A1 · Capital River as a fourth type
Your spec had Material and People rivers. I added Capital (Grant, Covenant, Trajectory, Grant Application) and Intelligence (Continuity, Intelligence, SCP Extraction). Two extra colour-coded river types so the board reads cleanly.
ADD A2 · Truth Ledger tail on the page
Last 20 field-level edits surfaced as a table at the foot of the board. Field, old → new, actor, timestamp. Auditable in one glance.
ADD A3 · Public JSON feed
/api/de.json exposes the whole board as JSON (read-only). Lets H.BLUE Bots, BOTS flipbook, and external dashboards consume the cadence without scraping.
ADD A4 · Health ring + health pill
Two visual representations of the 0–100 health: a coloured ring on the right of the card, and a coloured pill in the title row. Different scan distances.
ADD A5 · Blocker age thresholds rendered in colour
0–6 days = grey · 7–13 days = amber · 14+ days = red. Forces attention without a separate alert system.
ADD A6 · WoW arrow + spark on one line
Throughput, WoW, sparkline all next to each other so direction is unambiguous.
ADD A7 · Filter chips for state and river
One-click filter across 7 dimensions. No re-fetch — pure JS show/hide.
ADD A8 · Sovereign-only inline editor
Every card has a collapsible 15-field editor. Reads as part of the card, never a separate page. Same UX whether you're scanning or editing.
ADD A9 · Extract-New-Current preview endpoint
Three pre-baked candidates: Brand Equity Current · Covenant Audit Current · Partner Pipeline Current. Each with source → sink and a one-line reason.
ADD A10 · Owner_entity field on every row
Default H.BLUE Ltd. Surfaces SCP-2601 in the data layer, not just the design layer.
ADD A11 · MD-254 (this manual)
So when you come back in a week, the manual is one click away from the page (top nav: MD-254).

API Reference

MethodPathAuthPurpose
GET/dePublicRender the cadence board.
GET/api/de.jsonPublicRead-only JSON of all currents.
POST/api/de/<slug>/updateSovereignUpdate editable fields. Logs to Truth Ledger.
POST/api/de/extract-suggestSovereignReturns 3 candidate currents (preview).

Data Model (For Reds)

dynamic_currents (
  id SERIAL PK,
  slug VARCHAR(64) UNIQUE,
  title VARCHAR(200),
  ctype VARCHAR(32),          -- MATERIAL | PEOPLE | CAPITAL | INTELLIGENCE
  flow TEXT,
  throughput_value VARCHAR(64),
  throughput_unit VARCHAR(120),
  wow_pct REAL,
  spark VARCHAR(200),         -- 8 comma-separated numbers
  state VARCHAR(16),          -- GREEN | AMBER | RED
  health INTEGER,             -- 0..100
  blocker TEXT,
  blocker_owner VARCHAR(64),
  blocker_age_days INTEGER,
  next_milestone TEXT,
  milestone_done INTEGER,
  milestone_total INTEGER,
  depends_on TEXT,
  feeds TEXT,
  hblue_note TEXT,
  owner_entity VARCHAR(64) DEFAULT 'H.BLUE Ltd',
  updated_by VARCHAR(120),
  updated_at TIMESTAMP,
  created_at TIMESTAMP
)

dynamic_currents_log (
  id SERIAL PK,
  current_slug VARCHAR(64),
  field VARCHAR(64),
  old_value TEXT,
  new_value TEXT,
  actor VARCHAR(120),
  ts TIMESTAMP
)
    

Roadmap (v2 → v5)

v2 · Sealing UI for new currents

Confirm a candidate from the Extract preview, give it a slug, and it inserts itself into dynamic_currents.

v3 · Sunday Loop integration

Auto-bump blocker_age_days by 7 every Sunday for any current still blocked.

v4 · Cross-current alerts

If Carrot drops > 20% WoW, auto-add an H.BLUE note to Trajectory (because Trajectory feeds from it).

v5 · Public read-only embed

An <iframe>-able strip showing top 3 currents — for the public Carrot landing page.

What Not To Do

12
Currents Seeded
4
River Types
15
Editable Fields
11
Agent Additions
6
Workflows Documented
SCP-2601
Legal Container
H.BLUE Ltd
Owner Entity
249
Total MDs
The Final Line · 50/50
Architect: "Get it transferred over so it's already started without me having to input. Make a master document so I've got the full manual."
Agent: "Done. 12 currents seeded, 11 additions on top, owned by H.BLUE Ltd, sealed to the Truth Ledger, manual at MD-254. Open /de."
A1 🔵✅ · MD-254 SEALED · SCP-2600 + SCP-2601 · 17 APRIL 2026 · 50% / 50%
HANDSHAKE — witnesses
Handshake sealed.