eduKateSG | Future Master Publish

Register: FMP-S1-SG-000. This desk retains 74 inherited Ecosystem Atlas proposals, 50 WEP proposals, ten complete-route packets and 48 upgrade actions: 182 work records, not 182 new articles. Inherited queue · WEP queue · First route packets · 48 upgrades.

The eight Stage 1 publishing registers

Reconciled directory: 26 September 2026. Use the canonical register addresses below. Each desk returns here for publishing coordination; its established Atlas and exact article owners remain authoritative for their own subject. These are working records, not a count of unique articles or finished work. No homepage or menu change is required to use them.

Current accounting: 778 inherited/current-owner records + 282 retained WEP proposals + 86 complete-route packets + 12 SETC stage controls + 48 upgrade actions = 1,206 work records. The original 1,195-record snapshot is superseded by the import of BTT rows AT151–AT161. Shared upgrades are counted once. These totals do not claim 1,206 new articles, unique URLs, completed tasks or measured learning outcomes. Existing location-series and historical lane inventories remain separate until reconciled with their original IDs.

Stage 1 graph map: six first complete journeys

These are proposed reader routes and acceptance conditions, not claims that all journeys have passed testing. Links open the relevant packet sections; the displayed IDs identify the work within them. Read the current owner before creating or changing an article. A clear owner can be reached directly; a reader need not visit every desk.

Reconciliation and change control

BTT source discrepancy closed: the current Atlas identifies row 151 as ESAT and exposes rows 152–161 for ten board-specific routes. All eleven are preserved in BTT’s source-linked extension. This is source-inventory reconciliation, not a new audit of every destination’s factual content or frontend rendering.

Historical source recovery remains open: the earlier 101-row SETC and 114-row Yishun tables have not been recovered. Their current registers preserve identified owners and explicitly retain EN-HIST-001 and YI-HIST-114 as archival-reconciliation issues. Those historical counts do not establish that 101 or 114 articles are missing, nor do they block work whose current owner is already resolved. Do not fabricate old titles, renumber current owners or restart completed batches to satisfy an old total.

Single active register per site: Sengkang WP32658 and Orchard WP17346 are the designated unsuffixed owners. The duplicate copies WP32662 and WP17347 were returned to draft during the prior release and are excluded from all counts and work allocation. Their differently worded packet IDs must not overwrite active packet meanings. Preserve any useful draft text for deliberate reconciliation; do not operate parallel queues.

Before a publishing run, claim the task, record its actual owner and source aliases, and check the latest saved version. After release, inspect the stored body, public rendering where accessible, and required links; update the task and source Atlas deliberately. These are maintained editorial records, not an automatically synchronised database or background publishing service.

Federation Publish Gate v1.1

Desk: FED.WING.EDUKATESG. Before any task moves to BUILD, it must pass the federation gate below. Search demand can trigger inspection; it cannot bypass ownership.

1. Reader-job test. State the exact human job in one sentence. If the job is vague, HOLD.
2. Owner test. Search the live estate and Ecosystem Atlas. Prefer REUSE → DEEPEN → CONNECT → REFRESH before BUILD.
3. Page-role test. Classify the work as canonical owner, Atlas/hub, guide/manual, handbook, lesson, casebook, practice, assessment, reference, research note, local facet, current update or historical/archive.
4. Lifecycle test. Record PLANNED, CANONICAL LIVE, SUPPORTING LIVE, CURRENT UPDATE, SUPERSEDED, HISTORICAL, REPAIR REQUIRED or RETIRED.
5. ID and relationship test. Preserve/register the canonical ID and any Crosswalk Registry edges: owner, parent, specialist handoff, local facet, translation, practice, assessment, evidence, supersession and return.
6. Scope test. Record audience, subject/domain, stage/level, geography and time scope. Do not let a local, cohort or language facet silently become a universal claim.
7. Freshness test. Assign F0 STABLE, F1 INSTITUTIONAL, F2 LOCAL/PROGRAMME, F3 CURRENT RULE, F4 EVENT/LIVE or FH HISTORICAL and identify the review trigger.
8. Evidence test. Separate durable mechanism from changing fact; choose the appropriate source class and expose uncertainty where precision is not justified.
9. Quality test. A proposed canonical owner must pass the owner gate relevant to its role: job clarity, boundaries, mechanism, structure, dependencies, examples, failure modes, action/practice, transfer, assessment/evidence, sources, routing, machine consistency and distinct value.
10. Graph test. Record parent owner, prerequisites, next route, specialist/recovery/local handoffs and return route. No important page should enter the estate as an orphan.
11. Machine-identity test. Title, metadata, structured data and internal anchors must describe the same job and entity. Related wings are not alternate names for one another.
12. Release-receipt test. If ownership, meaning, current rules or major crosswalks change, create a change receipt and recheck dependent routes.

Wing-specific boundary: eduKateSG may BUILD systems, mechanisms, research, discovery and operating-architecture jobs. It must not duplicate eduKateSingapore’s public reference library, BTT/SETC specialist depth, Sengkang learner runtime, Yishun recovery or local implementation.

Final BUILD test: if an existing owner can satisfy the same job after a surgical update or stronger handoff, do not create another URL. SEO is telemetry for the gate; it is not permission to bypass the gate.

Release dependencies are different from reader routes

The six journeys in the directory show how a reader may move between resources. They are not a command to publish every destination in that exact order. For each bounded packet, use the dependency sequence below. English, Mathematics and other packets can advance independently once their own prerequisites are satisfied.

Dependency direction: G0 → G1 → G2 → G3 → G4. A maintained existing resource may satisfy a gate without a new article. Return, correction and optional specialist links are different edge types and may lead back; they do not create circular prerequisite requirements. An informational reference need not contain a quiz where the correct finish is a sourced answer or verified next action.

Task claim: record task ID, editor/run, start state, expected owner version and next action before drafting. Re-read immediately before creating a page. If WordPress unexpectedly appends a number to a slug, inspect the unsuffixed owner before treating the new page as canonical. Preserve useful conflicting work in draft for reconciliation rather than operating two live queues.

Concurrent-write reconciliation, 26 September 2026: Sengkang’s active register is WP32658; duplicate WP32662 was returned to draft. Orchard’s active register is WP17346; duplicate WP17347 was returned to draft. Neither duplicate contributes to the baseline counts. Their text is preserved; differently worded packet IDs in those drafts must not overwrite the active register’s task meanings.

Verification boundary: WordPress has returned the eight active page IDs and published states. That confirms stored publication, not anonymous front-end rendering, completed learning routes or implemented tools. Record any blocked public-page check as unverified. This register does not run background publishing, synchronise other tables automatically or override a protected homepage, menu, design or article.