Canonical owner routes

Atlas maps the estate; it does not replace the reader-facing owners. Use the canonical routes below when the job is to learn, explain, decide or act.

• eduKateSingapore Hub — resolve the reader’s next owner.
• Singapore Learning Library — school learning and curriculum routes.
• Vocabulary Learning System — meaning, use, retrieval and transfer.
• English World — language, reading, writing and literature.
• Mathematics World — reasoning, proof, structure and application.
• Science World — evidence, models, mechanisms and explanation.
• World Knowledge — sources, evidence, places, institutions and systems.
• Civilisation Atlas — institutions, capabilities, dependencies, coordination and long-term change.
• Parent Learning Support — family questions, routines and decisions.
• Singapore School Pathways & Calendar — live education-system rules, posting, calendars and stage transitions.
• Singapore Tuition Programmes — direct teaching and local programme routes.
• Research Collections — deeper evidence and specialist collections.
• Complete Content Index — exhaustive published-estate fallback.

Long-Horizon Atlas Law

Project Atlas is the public master cartography of eduKate. It should remain useful as the ecosystem grows for years: readers enter through a human question, the Atlas resolves the correct owner, and specialist or local sites deepen the route without duplicating the same canonical job.

• Build for durable educational coverage, not competitor parity. The target is a coherent education-and-civilisation knowledge system, not a larger version of a conventional tuition website.
• SEO is telemetry. Search data reveals missing language, weak ownership, unclear entities, broken handoffs and blind spots. It does not define the curriculum, the intellectual ambition or the site architecture.
• One owner, many routes. Discovery, diagnosis, recovery, reference, specialist depth and local implementation may live on different properties.
• Evidence before expansion. Strengthen a live owner or handoff before creating another broad page.
• Education expands into civilisation. School learning, adult learning, public knowledge, systems, science, mathematics, language and world knowledge should connect without collapsing into one undifferentiated site.

The operating companion is the eduKateSG Ecosystem Atlas, which carries the boundary ledger, build order and owner-governance work behind this public map.

Trust, Evidence and Knowledge Maintenance

A premier education system must remain useful after the page is published. eduKate therefore treats knowledge as maintained infrastructure: claims have owners, changing facts have dates and sources, contradictions are resolved rather than hidden, and corrections propagate through the route graph.

• Stable concepts: the canonical concept owner explains definitions, mechanisms and durable structure.
• Changing facts: current rules, dates, formats, pathways, prices, schedules and official requirements are checked against the strongest current source before they are presented as current.
• Evidence quality: source type, proximity, authority, currency, relevance, strength and uncertainty matter more than the number of links. Use How to Categorise Sources and How to Categorise Evidence as public reference routes.
• Official-system questions: use the official-source planning route before converting current policy or examination information into guidance.
• Verification and correction: factual conflicts route through corroboration, provenance and correction rather than being averaged together. See Editorial Fact-Checking and Source Verification.
• Research traceability: important claims should remain traceable into citations, references, metadata and research lineage through the scholarly linking route.
• Search performance: rankings, impressions and CTR are diagnostic signals about discoverability and intent alignment. They are not evidence that a claim is true or that a weaker page should define the architecture.

Knowledge-maintenance loop: claim → owner → source/evidence → publication → observation → contradiction or change → verification → owner update → handoff update → recheck. The goal is not merely to publish more pages; it is to preserve a trustworthy learning graph as the world, curricula and the ecosystem change.

Research → Practice → Evidence → Revision

eduKate should not separate research from teaching, and it should not confuse teaching experience with universal proof. The federation therefore uses a two-way research-to-practice loop: research informs a bounded teaching hypothesis; practice generates observations; those observations are interpreted in context; and the next version is revised, tested or rejected.

1. Question. Begin with a real learning, teaching or system problem.
2. Evidence. Use relevant research, official guidance and prior eduKate evidence without treating one study or one classroom as final truth.
3. Translation. Convert the evidence into a teachable or operational move with an explicit target and conditions.
4. Implementation. Run the move in the correct learner/tutor context through the Tutor System or the relevant subject/runtime owner.
5. Observation. Record what changed, for whom, under what conditions, and what did not change.
6. Interpretation. Separate implementation failure, learner variation, measurement noise and genuine mechanism failure.
7. Revision. Keep, narrow, adapt, replace or stop the practice.
8. Transfer. Only broaden the claim when the evidence survives new learners, tasks, delays and conditions.

eduKateSG owns the mechanism layer through Research–Practice Partnerships, Knowledge Brokering and Teacher Inquiry. Sengkang and the Tutor System own implementation and learner/tutor observations. eduKateSingapore owns public evidence, source and research-literacy routes. The purpose is a living education system that learns from both scholarship and practice without overstating either.

Global Growth Doctrine | Singapore as Reference, the World as Scope

eduKate begins in Singapore, but it should not remain bounded by Singapore. Singapore provides a rigorous reference environment: clear curricula, examinations, multilingual families, dense institutions, strong public systems and real teaching practice. The long-horizon goal is to build from that reference into a world education and knowledge system without pretending that one country’s structures are universal.

• Keep provenance visible. When a page describes Singapore rules, curricula, examinations, schools or institutions, say so clearly and keep the current-source discipline.
• Generalise mechanisms, not local facts. Learning, memory, transfer, reasoning, language, Mathematics, evidence and system design can travel; local regulations, paper formats and institutional pathways often cannot.
• Use specialist world routes. Bukit Timah Tutor carries world Mathematics curricula, examinations and advanced mathematical learning; Singapore English Tuition Centre carries world English language and examination routes; eduKateSingapore carries world knowledge and public reference.
• Crosswalk, do not collapse. Singapore, Cambridge, IB, AP, GCSE, national curricula and professional standards should be compared explicitly rather than blended into one fake global syllabus.
• Translate with meaning intact. Multilingual routes may change language, examples and cultural explanation while preserving the underlying concept, source trail and learning target.
• Local implementation remains local. Punggol, Sengkang, Yishun and Bukit Timah pages answer real local jobs; they are not templates to be copied across the world with place names swapped.
• World knowledge grows beyond schooling. University, research, work, professional practice, culture, technology and civilisation remain part of the same lifelong education graph.

Global control line: local evidence → durable mechanism → explicit scope → crosswalk → specialist/public owner → contextual adaptation → verification → transfer. The aim is not to make every page global; it is to know exactly which parts of an explanation can travel and which must remain anchored to place, system and date.

AI and Educational Technology | Capability Without Substitution

AI and educational technology are capability layers across the federation, not new owners. eduKateSingapore owns public AI literacy, tool choice and academic-integrity reference; eduKateSengkang owns whether AI-assisted study leaves the learner stronger; the Tutor System governs human professional judgement; Bukit Timah Tutor owns Mathematics education technology; and subject owners verify subject meaning. A tool is educationally useful only when the learner’s understanding, agency and independent performance survive after the tool is removed.

Federation handoff law

One reader job → one appropriate editorial owner → a useful next step when needed. eduKateSingapore carries the public knowledge map; eduKateSG carries systems, mechanisms, research, civilisation and governance; SETC and Bukit Timah Tutor carry specialist English and Mathematics. Sengkang carries learner-state diagnosis, practice, transfer and implementation evidence. Punggol carries the local family journey, town knowledge and place-based learning. Yishun begins with understanding and includes Well Being as well as recovery and rebuilding. Orchard helps resolve a question when the appropriate owner is not yet clear.

Local pages do not become national subject owners. A local page may contextualise, teach, help someone decide or route to a specialist. Preserve useful existing owners and link to the corresponding public or specialist estate when that is the next reader job. Punggol town information and Yishun Well Being do not have to become tuition or recovery funnels.

Specialist pages do not swallow the federation. SETC and Bukit Timah Tutor go deeper inside their domains; they return outward when the reader’s next job becomes public reference, another subject, learner-state work, recovery or local implementation. The Ecosystem Atlas boundary ledger governs these responsibilities; this public map makes the routes usable.

Long-horizon bridge: education → civilisation

eduKate is being built so today’s school-learning routes can grow into a larger public knowledge system without being replaced. Education is the first operating layer: a learner acquires language, mathematical reasoning, scientific explanation, evidence habits and study capability. Civilisation is the wider layer in which those capabilities are used to understand people, institutions, cities, technologies, economies, cultures, environments and long-term collective decisions.

• English → civilisation: language, literature, communication, media, law, culture, argument and public meaning.
• Mathematics → civilisation: quantity, models, finance, engineering, data, risk, optimisation, infrastructure and decision systems.
• Science → civilisation: evidence, mechanisms, medicine, environment, energy, materials, technology and planetary systems.
• World Knowledge → civilisation: history, geography, cities, institutions, governance, trade, conflict, cooperation and world systems.
• Learning → civilisation: memory, teaching, expertise, work, institutions, knowledge transmission, adaptation and future generations.

Atlas rule: do not create a second “civilisation version” of a subject that already has a canonical owner. Extend outward by scale and purpose. A school route may lead to a subject world; a subject world may lead to a system, institution or civilisation route; specialist depth may hand off to the correct eduKate property; every new layer must preserve provenance, evidence and a route back to the learner’s original question.

Owner mutation policy: update, supersede, archive or create

• UPDATE IN PLACE when the reader job and canonical intent are unchanged but facts, examples, syllabus references, evidence, dates, depth or internal routes need improvement. This is the default.
• SUPERSEDE only when an existing page cannot safely carry the current reader job because the qualification, programme, ownership boundary or information architecture has materially changed. The old page must point clearly to the successor where technically appropriate; history is not silently erased.
• ARCHIVE / HISTORICAL when the page describes a completed calendar, old syllabus, past score range or previous system whose dated state remains useful. Convert present-tense claims to dated provenance and provide the current-owner handoff.
• CREATE A NEW OWNER only when the reader job is genuinely new: a distinct intent, audience, stage, mechanism, examination task, pathway decision or specialist depth that the current owner cannot absorb without confusing its purpose.
• DO NOT CREATE merely because a keyword variant, year number, location adjective or “tips” phrasing exists. First test whether the canonical owner can answer the same job with a section, table, FAQ, local handoff or refreshed live-state block.

Collision gate before publication: search exact title, slug, core keyword, synonymous intent and likely legacy wording across the relevant property and federation. Resolve the canonical owner first. A new URL is the last architectural move, not the first.

Reader continuity after mutation: every superseded, archived or supporting page must still answer “where do I go now?” through an explicit canonical handoff and, where useful, a return to Project Atlas.

Spider → Web → Hidden → Deep → canonical return: the link-graph contract

Internal linking is not decoration. It is the transport system of Atlas. Every link should answer a reader-state change: where am I, what is underneath this, what is beside this, what comes next, and how do I return?

• SPIDER — discovery links: hubs and indexes expose the major branches that a reader is likely to seek next. A Spider link should resolve broad intent quickly, not bury the reader in every possible page.
• WEB — dependency and sibling links: canonical owners connect prerequisites, next concepts, parallel representations and closely related examination tasks. Web links show how knowledge fits together rather than merely sharing keywords.
• HIDDEN — diagnostic links: when an error commonly originates somewhere else, the owner links to the less-obvious prerequisite, learner-state route or representation that repairs it. Hidden links are justified by causality, not SEO adjacency.
• DEEP — mechanism and specialist links: school-facing owners descend into Science World, Mathematics World, SETC, BukitTimahTutor or another specialist/deep owner when the reader needs mechanism, proof, specialist teaching or greater technical depth.
• RETURN — canonical recovery links: deep, local, specialist, historical and supporting pages provide a route back to the canonical school-facing owner, estate hub or Project Atlas. No useful page should become a cul-de-sac.

Minimum obligations by page role

• Estate hub: link downward to its canonical lanes/owners, sideways only to genuinely adjacent estates, and upward to Project Atlas.
• Canonical topic owner: link to its estate hub, at least the meaningful prerequisite/next-step routes, any deeper mechanism owner, and the appropriate examination/pathway handoff when relevant.
• Supporting / local / diagnostic page: identify the canonical owner explicitly and return to it; do not silently compete for ownership.
• Deep mechanism / specialist page: preserve specialist depth, then return to the school-facing owner when the reader’s job becomes syllabus navigation or examination performance.
• Live-state owner: link to the durable system explanation underneath the changing date/rule and state the applicable cohort/date/source.
• Historical owner: preserve dated provenance and link to the current owner without rewriting the historical state as though it were current.

Link admission test: add a link only if it improves discovery, prerequisite repair, conceptual connection, specialist depth, pathway continuation or canonical return. Do not create dense cross-linking merely to increase link count. Atlas optimises for navigable meaning, not maximum edge density.

Atlas publication gate: before a page is allowed to become an owner

1. Reader job: state the exact question, task, stage and audience. If an existing owner already answers the same job, update it instead.
2. Collision check: search title, slug, core keyword, synonyms, legacy terminology, current terminology and likely neighbouring properties before creating a URL.
3. Ownership boundary: identify estate, hub, lane, canonical owner and specialist/local/recovery handoffs. Do not steal an established SETC, BukitTimahTutor, eduKateSG, Punggol, Sengkang or Yishun job.
4. Evidence and freshness: assign the appropriate F0–F4/FH class. Current rules, syllabuses, admissions, calendars and examination structures require official-source verification and an applicable cohort/date.
5. Search-language opening: the first three paragraphs should naturally carry the real reader/search language, define the page’s job and distinguish it from adjacent owners without keyword stuffing.
6. Substantive depth: major owners must explain definitions, mechanisms, dependencies, worked reasoning, failure diagnosis, transfer, practice/revision and relevant evidence. Length follows functional coverage; no padding.
7. Image family: Primary owners use the approved edukateprimary family; Secondary and later-stage owners use edukatesecondary. Existing valid featured images are preserved unless a separate image-replacement pass authorises change.
8. Link graph: satisfy the Spider/Web/Hidden/Deep/Return obligations appropriate to the page role.
9. Public-copy hygiene: internal production machinery, agent names and editorial controls stay silent in public copy. Public language remains reader-facing.
10. Publish/readback: after publication, re-read the live record. Confirm title, slug, status, featured image, metadata, body integrity and canonical links; resolve accidental duplicate slugs before Atlas registration.
11. Atlas registration: mark CANONICAL LIVE only after the live owner is verified. A planned row is not evidence that a page exists.
12. Maintenance handoff: record what changes next—evergreen deepening, measurement, freshness review, official-state watch or historical preservation.

Fail closed: if ownership, evidence, freshness or safe editing cannot be resolved, hold the write. A missing page is cheaper to repair than a duplicate canonical owner, a stale current-rule page or a destructive rewrite.

Measurement, repair and retirement protocol

Publication is not completion. Atlas owners enter a measurement cycle, but traffic alone never decides ownership. A canonical page may serve a small but essential reader job; a high-traffic page may still be structurally wrong, stale or cannibalising another owner.

• Search discovery: impressions, query families, ranking distribution, CTR and whether Google is matching the intended reader job rather than an accidental one.
• Coverage: whether the owner actually resolves the intended definitions, mechanisms, dependencies, examples, diagnosis, transfer and next-step questions.
• Reader continuation: whether the page provides meaningful routes into prerequisites, deeper mechanisms, practice, pathways and canonical returns instead of ending the journey.
• Freshness: whether facts, syllabuses, dates, programme rules, terminology and official references still match the page’s declared freshness class.
• Collision: whether another page is beginning to answer the same job more clearly, creating cannibalisation or ambiguous ownership.
• Estate role: whether the page still performs the federation job assigned to its property, or has drifted into another site’s canonical territory.

Allowed outcomes after review

• KEEP: owner is structurally correct; continue measurement.
• HARDEN: preserve URL and ownership, but improve opening language, coverage, evidence, internal links, metadata or transfer routes.
• REFRESH: update a live-state or freshness-sensitive section while preserving the durable owner.
• REPAIR ROUTING: keep content but correct parent/child/sibling/deep/return links or federation handoffs.
• MERGE: consolidate two pages only when they genuinely perform the same reader job. Choose the stronger canonical owner, preserve useful unique material and provide an appropriate successor path.
• SUPERSEDE: replace the current owner only when the reader job or system itself has materially changed and update-in-place would misrepresent the new architecture.
• HISTORICAL: preserve a dated state whose past facts remain useful; remove present-tense authority and route to the current owner.

Do not delete useful history to make the graph look tidy. Preserve provenance when it helps readers understand an old syllabus, examination, posting range, calendar or policy state. Atlas distinguishes current truth from historical truth instead of pretending only one ever existed.

Review windows: F0 evergreen owners are reviewed when evidence, search behaviour or architecture indicates a need; F1/F2 pages receive periodic institutional/programme checks; F3/F4 live-state owners are reviewed against their declared validity window and official-source triggers; FH pages are checked for correct historical labelling and current-owner handoff.

Editorial-owner registry contract

Every durable Atlas owner should be representable as a registry record even when the public page never shows an internal ID. The registry exists to make editorial ownership auditable across thousands of pages and multiple properties. It does not set search-engine canonical tags, redirects or indexing directives.

• Internal owner ID: stable estate/lane identifier where one exists.
• Public owner URL: the live reader-facing page preferred for this editorial job. This is not, by itself, a technical canonicalisation instruction.
• Reader job: the exact intent the owner resolves.
• Estate / property: eduKateSingapore public library/cartography, eduKateSG systems/mechanisms/research/governance, SETC, BTT, Sengkang, Punggol, Yishun, Orchard or another authorised property.
• Parent owner: the editorial hub or lane immediately above it.
• Dependencies: prerequisite owners whose knowledge or state is required.
• Deep handoff: mechanism/specialist owner when the page intentionally stops at school-facing or routing depth.
• Freshness class: F0, F1, F2, F3, F4 or FH, with cohort/date/source where applicable.
• Status: planned, owner-live, supporting, superseded, historical or hold.
• Predecessor / successor: explicit editorial relationship when a syllabus, qualification, calendar or architecture changes.
• Verification: last checked date and authority for freshness-sensitive owners.

Public URL and internal ID are different things. A lane may map to an existing page rather than create a new URL. Conversely, one public hub may carry several internal registry responsibilities. The registry prevents namespace design from forcing unnecessary public pages.

Atlas table rows are registry views, not permission to publish or technically canonicalise. The publication gate controls creation; any redirect, noindex or canonical-tag decision requires its own evidence and approval under the federation’s technical rules.

Estate health audit: what Atlas checks after the build

Atlas is healthy only when the graph remains usable after publication. Each estate should be periodically scanned for structural defects, not merely page count.

• ORPHAN: a useful owner exists but no appropriate hub/index exposes it.
• DEAD END: a page answers its immediate question but provides no meaningful next/deeper/return route.
• COLLISION: two pages materially compete for the same reader job or canonical query family.
• STALE STATE: a live-state page still speaks with current authority after its cohort, calendar, syllabus or rule has changed.
• BROKEN DEPENDENCY: an advanced owner assumes prerequisite knowledge but does not expose the repair route.
• MISSING DEEP HANDOFF: a school-facing owner stops where mechanism/specialist depth is clearly needed but gives no route downward.
• MISSING RETURN: a local, specialist, mechanism, historical or supporting page does not point back to the current canonical owner/hub.
• PROPERTY DRIFT: a page begins performing another eduKate property’s canonical job instead of handing off.
• REGISTRY DRIFT: Atlas status, public URL, predecessor/successor state or internal ownership no longer matches the live CMS.

Audit order

1. Verify canonical owner and live URL.
2. Verify hub discovery.
3. Verify prerequisite and sibling Web routes.
4. Verify Hidden diagnostic routes for known failure causes.
5. Verify Deep specialist/mechanism routes.
6. Verify canonical return.
7. Verify freshness class and official-source state.
8. Verify Atlas/registry status against the live page.

Repair priority: collision and stale-state defects outrank link-density improvements because they can mislead readers about ownership or current truth. Orphans and dead ends come next. Decorative cross-linking comes last.

Definition of done: published is not finished

• PUBLISHED: a live URL exists and readback confirms the intended body, title, slug, metadata and image.
• HUBBED: the correct canonical hub/index exposes the owner and the owner identifies its parent estate.
• CONNECTED: prerequisite, sibling, diagnostic, deep and return links satisfy the page role without indiscriminate edge density.
• HARDENED: collision, freshness, federation boundary, first-three-paragraph intent, source discipline and public-copy hygiene have been checked.
• REGISTERED: Atlas/registry records the actual live owner, status, freshness class and predecessor/successor state where relevant.
• MEASURABLE: the page has a defined future review trigger—search/reader evidence, institutional change, annual state change or architectural audit.
• DONE FOR NOW: all of the above are true and there is no unresolved higher-priority defect. “Done” means stable enough to enter maintenance, not permanently frozen.

An estate is complete only when its intended owners are published + hubbed + connected + hardened + registered + measurable. A large pile of live URLs without those properties is inventory, not an Atlas.

Change control for concurrent Atlas builds

Multiple estate branches may work on the ecosystem at the same time. Atlas therefore uses optimistic, content-matched editing rather than assuming a block index, page position or earlier snapshot is still current.

• Re-read before write: fetch the current live block map immediately before a surgical edit.
• Match by identity: locate the target by anchor, heading, distinctive content or block hash; do not trust an old numeric index after another branch has edited the page.
• Use expected state: where supported, send the current modified timestamp/content hash/block hash so a stale write fails rather than overwrites newer work.
• Fail closed: if the expected block moved, changed type or no longer matches, stop and re-resolve it. Never widen a surgical edit into a full-page rewrite merely to force the change through.
• Re-read after write: verify that the intended block changed and adjacent blocks remained intact.
• Idempotence: before inserting a route, status note or governance block, test whether it already exists. A repeated continuation should converge, not duplicate.
• Branch reconciliation: when another branch has already published the intended owner, switch from CREATE to VERIFY / HARDEN / HUB rather than generating a second page.

Operational rule: stale state is information, not an obstacle. A refused optimistic write means the estate changed and must be re-read. Atlas protects newer valid work before it protects the convenience of the current batch.

Batch-state ledger: how a continuation resumes safely

• CREATE: collision gate is clean and a genuinely new canonical owner is authorised for publication.
• VERIFY: the intended owner already exists; inspect live title, slug, body, metadata, image, freshness and ownership before doing anything else.
• HARDEN: preserve the canonical URL while improving evidence, opening language, scope boundary, metadata, image, diagnosis, freshness or internal graph.
• HUB: owner is sound but discovery/return/dependency routing is incomplete; repair the graph without rewriting the owner.
• HOLD: ownership, source authority, freshness, collision or safe-edit state is unresolved. Do not publish or force a destructive edit.
• COMPLETE: the batch satisfies Atlas’ definition of done and enters maintenance/measurement.

Every continuation should infer the current state from the live CMS + Atlas registry, not from the last conversational instruction alone. If a parallel branch moved CREATE to live publication, the next continuation automatically becomes VERIFY/HARDEN/HUB.

Resume marker: the meaningful stopping point is the first unresolved owner, graph defect, freshness trigger or HOLD condition—not simply the last URL printed in chat.

Evidence provenance: authority, cohort and interpretation

Atlas separates what an authority states, what eduKate explains from it, and what remains uncertain. A source does not become current merely because it is official; its date, cohort, syllabus code and validity window must match the claim.

Source hierarchy by claim type

• Rules, syllabuses, examination formats, calendars, admissions and posting: use the responsible authority first—MOE, SEAB or the relevant official institution.
• School-specific programmes, subjects, CCAs and current arrangements: use the school’s current official material, while distinguishing school information from national policy.
• Scientific, mathematical, linguistic or educational mechanisms: prefer primary/authoritative academic, institutional or reference evidence appropriate to the claim; use eduKate’s canonical mechanism owner to synthesise rather than copy.
• Search demand and discovery behaviour: use current search-performance evidence where available, but never let query volume override factual ownership or reader need.
• eduKate pedagogy and operating methods: identify these as eduKate frameworks or teaching interpretations rather than attributing them to MOE/SEAB unless the authority actually states them.

Claim-state labels

• OFFICIAL CURRENT: directly supported by the applicable current authority/source.
• OFFICIAL DATED: accurate for a named past cohort/year/system and preserved with provenance.
• EDUKATE INTERPRETATION: analysis, explanation, teaching architecture or practical implication derived from evidence; do not present it as an authority quotation.
• STATUS TRACKER: the future/current state is not yet officially released; state what is known, what is pending and the last verification point without guessing.
• UNCERTAIN / HOLD: evidence conflicts, scope is unclear or authority cannot yet be resolved; do not convert uncertainty into a confident public claim.

Cohort inheritance rule: a 2026 syllabus does not automatically describe a 2027 SEC candidate; a previous-year posting range does not become the current cut-off; a 2026 school calendar does not predict 2027 dates. Reuse mechanisms where durable, but re-verify institutional state.

Source-to-copy rule: cite or link the authority where navigation helps, paraphrase accurately, and keep eduKate’s explanation distinct. Atlas is a knowledge system, not a mirror of official documents.

Claim-expiry triggers: when Atlas must re-verify

• New syllabus / subject code: recheck scope, terminology, assessment structure and predecessor/successor routes.
• MOE / SEAB annual release: refresh calendars, examination dates, registration windows, posting information and applicable cohorts.
• Posting / admissions cycle completes: convert forecast/status-tracker language into dated actual-state evidence where official results exist.
• School-year rollover: recheck pages carrying “this year”, “next year”, age/year-level transitions or cohort-specific advice.
• Programme redesign: recheck GEP/high-ability identification, Full SBB, SEC, post-secondary admissions, JC/UAS and other pathway-system owners when policy changes.
• Official page materially changes: verify whether eduKate’s interpretation and linked guidance still match the authority.
• Canonical collision appears: re-open ownership even if both pages are individually accurate; reader ambiguity is itself a defect.
• Search intent shifts materially: inspect whether the owner still resolves the query family; harden wording/routing before considering a new URL.
• Reader-state evidence exposes a gap: repeated failure to find prerequisites, next steps or current pathways triggers graph repair.

Expiry does not mean deletion. It means the affected claim returns to VERIFY. Evergreen mechanisms may remain untouched while only the live-state section, cohort label, source note or successor route changes.

Progressive disclosure: make a huge ecosystem feel small

Atlas can contain thousands of owners without showing thousands of choices at once. Navigation should reveal only the depth needed for the reader’s current job, then open the next layer deliberately.

• Layer 1 — human route: subject, stage, reader state or pathway decision. The reader should recognise the doorway without knowing eduKate’s internal taxonomy.
• Layer 2 — canonical lane: year level, examination paper, topic family, programme or decision branch.
• Layer 3 — diagnostic branch: prerequisite, failure mode, representation, skill or recovery route.
• Layer 4 — deep owner: mechanism, specialist explanation, worked laboratory, evidence, advanced Mathematics/English/Science depth or technical manual.
• Layer 5 — return/continuation: practise, assess, choose the next topic/pathway, or return to the canonical hub/Atlas.

Hub rule: expose the smallest set of high-information choices that covers the reader’s likely next jobs. Do not dump the registry onto the page. A registry is exhaustive; navigation is selective.

Deep-page rule: the deeper the reader travels, the more specific the content may become—but the route back must become clearer, not weaker.

Choice-overload test: if two links appear equivalent to a reasonable reader, clarify their jobs or collapse the choice. Atlas should reduce uncertainty at every click.

Route-completion test: every search landing must recover the map

Readers rarely enter an ecosystem through its front door. Search may land them on a deep topic, old calendar, local guide, diagnostic article or specialist mechanism. Every useful landing page should therefore be able to reconstruct enough context for the journey to continue.

1. Orient: what is this page, who is it for, and what job does it own?
2. Resolve: answer the immediate question substantially before demanding another click.
3. Repair: expose the prerequisite/diagnostic route if the reader cannot use the answer yet.
4. Deepen: expose mechanism or specialist depth when the current page intentionally stops short.
5. Continue: show the next logical practice, topic, examination or pathway action.
6. Return: expose the canonical hub or Atlas so the reader can recover the wider map.

Search-entry principle: no canonical owner should require prior knowledge of eduKate’s site architecture to be useful. The page must work as a standalone landing and as a node in the federation.

Completion signal: the route is successful when the reader can answer “what did I learn, what remains weak, and where should I go next?” without guessing.

Production Ledger II: Primary Science Student Readers · 3/3 LIVE

Registered 26 September 2026 after a live-estate gap audit. The existing Primary Science for Students hub already owned the P3→P6 child-facing route, but only Primary 3 had a dedicated complete reader. Primary 4, Primary 5 and Primary 6 were explicitly marked as orientation summaries awaiting their own student versions. Ledger II resolves that genuine reader-job gap without creating another Science hub.

Ownership boundary: these three pages own the clear student explanation layer. The Primary Science Specialist Library retains deeper mechanism and teaching detail; the Science Learning Library retains concept/diagnosis routes; tuition and locality pages retain delivery and service intent. Do not create another P4/P5/P6 “student guide” for the same job.

Next action: mature rows 172–174 in place from FOUNDATION OWNER toward DEEP OWNER by adding further worked examples, misconception diagnosis, retrieval, transfer and specialist handoffs where they materially improve learning. Expansion happens inside these owners; it does not justify competing duplicates.

Owner maturity: live does not mean finished

Project Atlas separates ownership status from content maturity. A canonical owner can be live because the correct page, URL and responsibility have been resolved while still requiring deeper examples, diagnosis, evidence, practice, source renewal or transfer work. This prevents eduKate from creating duplicates merely because a live owner is not yet deep enough.

Depth standard: major canonical teaching and knowledge owners normally progress toward 20,000+ substantive words when that depth improves definitions, mechanisms, worked examples, diagnosis, transfer, practice, revision, evidence and long-term usefulness. Word count is not a target for its own sake: routers, status trackers and narrow reference pages should remain as long as their job requires and no longer.

Current priority: Ledger I’s first 171-owner build is complete, and Ledger II adds three separately registered Primary Science student-reader owners (rows 172–174), bringing the current Atlas registered-route total to 174. Secondary Science has completed Maturity Pass 2, while Singapore School Pathways & Calendar has completed its freshness pass; the six opening Secondary Science teaching owners now include worked reasoning, diagnostic ladders, misconception repair, practical/data work and world-return routes while remaining FOUNDATION owners for future deepening. English and audited Mathematics collisions are resolved by owner/support roles. The next operating job is systematic owner maturation, live-state renewal, measured collision audits, reader-behaviour analysis and selective expansion toward the 20,000+ standard only where additional depth improves the reader job.

Six owner-maturity gates

• 1. Ownership gate: one canonical owner, clear boundary, no unresolved competing page for the same reader job.
• 2. Evidence gate: claims point to appropriate primary or authoritative sources; live-state claims carry a verification date and expiry horizon.
• 3. Teaching/explanation gate: definitions connect to mechanism, worked examples, failure modes, diagnosis and transfer rather than stopping at summary prose.
• 4. Routing gate: the owner can send readers upward to its hub, sideways to adjacent owners and downward to deeper mechanisms without becoming a link farm.
• 5. Independence gate: the page helps the reader do something—solve, explain, compare, verify, practise, decide or stop—rather than creating permanent dependence on more pages.
• 6. World-return gate: where appropriate, the owner shows how the school concept survives outside the examination and connects into real systems, evidence, institutions or civilisation without creating a duplicate “world” article.

Owner Maturity Wave 02 — 27 September 2026

This wave continues the Atlas rule deepen owners before multiplying URLs. Four high-value canonical owners have completed a second in-place maturity pass. No replacement or competing owner was created.

Maturity status: the three teaching owners are stronger FOUNDATION owners; the Additional Mathematics page is a stronger ROUTER / GATEWAY whose job is deliberately smaller than a specialist textbook. Future expansion should occur only when it adds new worked reasoning, evidence, practice, diagnosis, transfer or routing value. Do not manufacture another generic composition, Primary vocabulary, Editing or Additional Mathematics gateway for the same jobs.

English Exam Maturity Wave 03 — 27 September 2026

Estate B continues in owner-maturity mode. Three O-Level examination owners have completed a second in-place teaching pass. The URLs, ownership boundaries and supporting routes remain unchanged; the new work adds capability rather than another competing article.

Status: all three remain FOUNDATION teaching owners. Their next maturity step is not more decorative examples; it is further evidence, varied transfer, diagnosis and independent practice only where those additions materially improve performance. Continue these URLs in place.

PSLE English Maturity Wave 04 — 27 September 2026

Three PSLE Paper 1 / Paper 2 canonical owners have completed a second in-place teaching pass. This packet also corrected a legacy title that implied a universal fixed six-point Situational Writing task. The current owner now reflects the official task contract—purpose, audience and context—while retaining eduKate’s six-question planning checklist as a teaching tool rather than an examination claim.

Status: all three remain FOUNDATION teaching owners. Continue maturing these same URLs only where additional examples, diagnosis, retrieval or transfer add a new capability; do not create duplicate generic PSLE Situational Writing, Grammar Cloze or Synthesis pages.

Maturity Queue II: deepen owners before multiplying URLs

Ledger I’s first 171 registered routes are live, and Ledger II separately registers three Primary Science student-reader owners as rows 172–174; the current Atlas registered-route total is therefore 174. Atlas now prioritises owner maturity. New URLs are justified only by a genuinely new reader job. Otherwise the existing owner is expanded in place.

1. Secondary Science Shelf and concept owners — MATURITY PASS 2 COMPLETE. The Shelf, Lower Secondary map and Physics/Chemistry/Biology indexes are live; the six opening concept owners now contain worked reasoning, misconception/error diagnosis, practical design, transfer labs, mixed assessment labs and Science World / civilisation handoffs. Continue deepening these same URLs toward full DEEP OWNER status; do not create duplicate topic pages.
2. Singapore School Pathways & Calendar — FRESHNESS PASS COMPLETE. All 13 registered owners now carry an explicit F1/F3/F4 verification state or review trigger, and the hub exposes a route-level freshness matrix. Continue deepening durable explanations in place while updating date-sensitive owners from MOE/SEAB rather than cloning yearly pages.
3. Evidence and refresh clocks — EXTENSION PACKET 01 COMPLETE. School Pathways initial pass remains complete. The canonical PSLE Composition method, English Exam-Paper Map and O-Level / SEC G3 Editing now carry visible claim-level F3 verification receipts dated 27 September 2026 with official SEAB source links and refresh triggers. Continue the same discipline to other syllabus, admissions, calendar, programme and current-rule owners across eduKateSingapore.
4. English exam owners: Hybrid Essay, Unseen Poetry, Prose Analysis and Literature PEEL have completed maturity pass 4 with 2026 O-Level → 2027 SEC source control. Continue the same depth discipline on prescribed Literature, IGCSE and IB owners before considering new “tips” URLs.
5. Mathematics locality owners: measure the clean-slug canonical pages after duplicate suppression; preserve noindex deep dives only when they add a distinct teaching lens.
6. Education → civilisation bridge: add outward routes only where a school concept naturally becomes a question about institutions, infrastructure, technology, culture, evidence or long-term collective capability.

Freshness Extension Packet 02 — 27 September 2026

Project Atlas has extended visible claim-level freshness control beyond the completed School Pathways packet. The rule is unchanged: date the changing claim, not the entire teaching page. Durable mechanisms remain on stable canonical URLs; current syllabus, qualification and format statements carry a source, verification date and refresh trigger.

Next freshness work: extend the same claim-level protocol to other high-value syllabus, programme, admissions and current-rule owners only when they actually contain time-sensitive claims. Do not add decorative timestamps to F0 teaching mechanisms.

Freshness classes for evidence-sensitive owners

Every canonical owner has a freshness job as well as a content job. Project Atlas inherits the controlled classes in the Ecosystem Atlas Freshness, Version and Review Protocol and the eduKateSingapore Future Master Publish gate. The same code must mean the same thing across the federation. These are maintenance requirements, not a claim that every owner has already been checked or that automatic monitoring is running.

Current examples and claim-level scope

• F3 current rules and schedules: MOE School Holidays & Term Dates 2027, PSLE 2027 Dates & Timetable, and P1 Registration for 2027 Entry. A time-critical event or availability statement within these owners requires the tighter F4 active-window review.
• F3 current-rule transition claims: 2026 O-Level → 2027 SEC, After SEC / 2028 PSE, and Primary 3 High-Ability Identification. Separate confirmed changes from pending implementation details; a transition is not a separate meaning for the F3 code.
• F1 institutional explanation with F3 current eligibility or admissions claims: Higher Mother Tongue and JC Subject Combinations. Apply the tighter review requirement to the changing claim, not a blanket freshness claim to the whole page.

Operating rule: when a live-state owner becomes stale, refresh the existing canonical URL. Do not create a competing page merely because the calendar year changed unless the reader job itself changes. A recent modification timestamp is not a source-verification receipt. Historical material uses FH, not F4; an annual calendar is not F2 merely because it changes every year.

Federation Operating Contract | One Educational Reality, One Clearest Authority, Many Interfaces

Project Atlas treats the eduKate estate as one federated educational system rather than a collection of independent websites. The governing principle is one clear editorial owner for each reader job, with many legitimate routes for different people, learner states, locations, examinations and purposes. This public summary follows the eduKateSG Ecosystem Atlas boundary ledger; it does not replace that governance record or the current eduKateSingapore work register.

The federation has different jobs, not competing copies

• eduKateAI / Orchard: human reception, question routing, owner resolution and return paths. It is the eighth federation wing, not another subject-content estate.
• eduKateSG: systems, mechanisms, research, broad discovery, education and civilisation, alongside operating governance. This is an expandable knowledge estate, not merely a supporting administrative page.
• eduKateSingapore: public master cartography, knowledge, evidence, reference, Learning Manuals, Science World and world-library routes. Public explanation does not automatically transfer every mechanism or specialist job here.
• Bukit Timah Tutor: specialist Mathematics, mathematical dependencies, representation, proof, applications, pedagogy, curriculum crosswalks and advanced pathways.
• Singapore English Tuition Centre: specialist English across language mechanism, reading, writing, oral communication, comprehension, Literature/GP, pedagogy and examination performance. Its English Atlas already exists.
• eduKateSengkang: learner state, first-weak-link diagnosis, practice, transfer, assessment evidence, examination craft, independent performance and implementation evidence. Its job is wider than sequencing alone.
• eduKateYishun: understanding-first interpretation, Well Being, recovery, rebuilding, second chances and skills conversion. Well Being also serves belonging, curiosity, relationships, play and ordinary enjoyment without requiring a crisis or a broken learner.
• eduKatePunggol: Punggol family life, town and place-based learning, local education, consultation and tuition implementation. The Complete Punggol Guide serves town questions in their own right, not as disguised tuition enquiries.

The Tutor System and technical Tutor Handbook are the shared human-support layer within Sengkang, not a ninth federation wing. They connect an identified instructional need to professional teaching, evidence, review and appropriate independence.

These roles may overlap in subject matter without colliding in responsibility. A Yishun article may investigate why an algebra experience failed while BTT supplies mathematical depth; Punggol may explain a local English-support decision while SETC supplies specialist English. The distinction is the reader job and evidence required, not a ban on mentioning the same concept in different places. Preserve legitimate public-reference, specialist, local and established legacy owners.

Editorial ownership is not technical canonicalisation. Naming a preferred resource here does not instruct a search engine to select it as the canonical URL, nor authorise redirects, noindex or cross-domain canonical tags. Those are separate technical decisions requiring their own evidence and approval. See Google’s canonicalisation documentation for the distinct search-engine meaning.

Four object families

Every substantial future object should be understandable primarily as one of four families: Knowledge explains what is true or how something works; Process explains what a learner, tutor or parent should do; State identifies the person’s present situation, including but not limited to learning difficulty; Interface translates a particular human, local, annual or search intent into the correct route. These are explanatory lenses, not a replacement namespace or a new registry of page types.

• Owner: the preferred editorial treatment for a defined reader job.
• Router: helps the reader choose the appropriate owner.
• Interface: serves a distinct local, year, examination, parent, tutor or search intent without recreating the whole subject.
• Bridge: teaches a difficult transition between two already-existing capabilities.
• Boundary: clarifies when one problem, state or jurisdiction becomes another.
• Protocol: turns knowledge into a repeatable learning, teaching, revision or recovery procedure.
• Resource: examples, exercises, lists, references and supporting material.
• Recovery object: investigates the person, task and conditions, offers a bounded repair when warranted, retests and provides a useful return route.

BUILD, CONNECT, REPAIR, PROTECT

PROTECT → CONNECT → REPAIR → BUILD is a preservation-first decision shorthand, not a replacement for the registered execution order REUSE → REPAIR → REFRESH → DEEPEN → CONNECT → BUILD. Do not send readers into a known broken destination merely to connect first. Preserve healthy work, repair the actual defect, and build only for a demonstrated missing job.

1. PROTECT. Preserve proven URLs, ranking roles, useful legacy explanations, frozen interfaces and stable canonical scope. “Upgrade” never means changing a healthy object merely because it can be made larger.
2. CONNECT. Resolve orphans, missing inbound routes, weak handoffs and absent continuations before multiplying URLs.
3. REPAIR. Correct stale examination language, wrong parents, authority collisions, dead ends, missing return routes and unclear scopes surgically.
4. BUILD. Create a new object only when the existing estate cannot perform the required educational job without distortion.

The admission test for a new page is therefore strict: What concept is involved? Does an adequate owner already exist? What reader intent or educational job is genuinely different? Is this an owner, interface, bridge, protocol, router or recovery object? Where does it enter the graph, where does it send the reader next, and what existing page would it otherwise collide with? A broad role statement never authorises the deletion or wholesale rewriting of a proven legacy owner.

The learner-state loop

Atlas is not only a map of subjects. It is also a map of changing learner state. A learning route can follow enter → orient → investigate where necessary → learn → practise → apply → assess → progress. When evidence warrants recovery, the route can continue recover → retest → return. Human support can enter through the Tutor System and Tutor Handbook. A reference question, town visit or Well Being question may simply end in understanding, enjoyment, belonging or a useful decision; it does not need to complete an examination or recovery loop.

A poor result is not by itself a diagnosis. The difficulty may concern knowledge, interpretation, representation, retrieval, transfer, timing, access, task conditions or a mistaken adult expectation. Investigate rather than assign a fixed identity. Keep the learner’s voice and necessary accommodations; reduce unnecessary prompting only when the evidence supports that change. Recovery is not a label for the person and is not the entirety of Yishun.

Every important route must close the loop

• Entry state: what does the reader know, believe, want or observe when entering?
• Target owner or process: which part of the federation is responsible for the next job?
• Action: what should the learner, parent, tutor or general reader do?
• Evidence: when the route claims learning or improvement, what observable change supports that claim?
• Alternative or failure route: what happens when the route is unsuitable or the expected evidence does not appear?
• Return or exit: where does progression resume, or when is the present question sufficiently answered?

A topic is not system-complete merely because an excellent article exists. Major learning topics need an appropriate combination of knowledge → learning/application → evidence → failure handling → recovery where warranted → verification → next state. Not every niche concept, reference resource or Well Being route needs every layer. A stored link is evidence of a connection, not evidence that a learner improved.

Change control and architectural regression

Atlas distinguishes three modification modes: PRESERVE for healthy or protected objects; SURGICAL for bounded repairs; and REBUILD only when the current implementation can no longer perform its approved role. The greater the impact on other routes, the smaller the default change budget. Read the latest page and its dependencies before changing a hub, Atlas or federation boundary; preserve concurrent work outside the approved repair.

A page can improve while the estate regresses. A second “ultimate” owner for the same job, a local interface that becomes a duplicate subject encyclopedia, a recovery route without a useful return, or a homepage that becomes harder to navigate are regressions even when individual prose improves. The estate therefore checks structure, ownership, coherence and currentness—not only writing quality.

The stop-editing condition

An object can be treated as STABLE within a stated audit scope when its role is clear, its relevant routes have been checked, changing claims have appropriate evidence, and no material collision remains in that scope. Publication alone does not establish this state. Protect stable work; reopen it for new evidence, changing facts, broken routes or an explicit architectural decision, not because every branch must leave a larger footprint.

What Project Atlas now optimises

Project Atlas does not optimise for maximum URL count. It aims for useful educational coverage with clear editorial responsibility and a comprehensible route between a real human question and the appropriate next action. Each choice should reduce uncertainty rather than merely expose more links.

Final operating law: create only when knowledge or intent is genuinely absent; connect when the asset already exists; repair when role, route or currentness is wrong; protect when the system is healthy. Keep public vocabulary maps and established application pages on their current URLs, and use the eduKateSG Vocabulary Hub for the learning/mastery mechanism. No conceptual boundary change silently retires an existing owner.

Scope — 27 September 2026: this is the public summary of the current federation rules, not certification that every branch, source, URL or learner journey has been audited or automatically brought into compliance. Record bounded work and verification in the current publishing registers. Use the existing link-graph contract and publication gate; no new master map is required. Less-obvious diagnostic relationships may produce useful visible links, but “Hidden” never means invisible SEO links, concealed text or an unimplemented database described as live.

PSLE Editing Maturity Wave 05 — 27 September 2026

The canonical PSLE Editing | Spelling & Grammar Error Types, Detection and Repair owner has completed a second in-place maturity pass. The existing URL, title, metadata, indexability, earlier teaching material and exam-paper ownership were preserved; no competing Editing page was created.

Status: PSLE Editing remains a FOUNDATION teaching owner, now materially stronger in connected-passage execution and independence. Further work should deepen this same URL only when new evidence, diagnosis, transfer or practice adds capability. Do not create another generic PSLE Editing owner for the same reader job.

PSLE Grammar MCQ Maturity Wave 06 — 27 September 2026

The canonical PSLE Grammar MCQ: 10 Grammar Rule Families to Control owner has completed a further in-place maturity pass under the current owner-first standard. Its existing search-language opening, title, metadata, indexability, rule-family map, earlier diagnostic material and assessment lab were preserved.

Status: FOUNDATION teaching owner, materially stronger in discrimination, evidence control and transfer. Continue this same URL only when additional work adds a distinct capability; do not create another generic PSLE Grammar MCQ owner or inflate the page merely to reach a word-count target.

PSLE Reading Maturity Wave 07 — 28 September 2026

Two canonical PSLE reading owners have completed bounded in-place maturity passes above the current Clementi-style search/usefulness floor. Their URLs, titles, metadata, indexability, existing teaching sections, FAQs and ownership boundaries were preserved. No replacement reading owner was created.

Status: both remain FOUNDATION teaching owners. Visual Text now has stronger multimodal evidence control; Open-Ended now has stronger evidence-to-answer calibration. Future work should preserve these URLs and add only genuinely new evidence, diagnosis, transfer or independent-practice capability. Do not create generic duplicate PSLE reading owners.

Clementi SEO+ Measurement Gate | Protect What Google Already Understands

Measurement baseline — finalised Google Search Console data, 28 August to 24 September 2026: the established Secondary 1 Mathematics Tutor Clementi page recorded 23 clicks from 141 impressions, 16.31% CTR and average position 8.65. For the exact query “secondary 1 mathematics tuition clementi”, the page recorded 12 clicks from 16 impressions, 75% CTR and average position 2.56. For “secondary 1 mathematics tutor”, it recorded 8 clicks from 27 impressions, 29.63% CTR and average position 6.07. These are Search Console performance signals for the stated period, not search-volume, conversion or revenue claims.

What transfers from Clementi: exact stage + subject + intent + location must be unmistakable in the title and first three paragraphs; the page must then earn that click with real educational depth. Length alone is not the standard. A Clementi SEO+ page should make the learning problem explicit, diagnose before prescribing, teach a mechanism, show practice and transfer, provide evidence of progress, answer the parent’s real decision questions, use truthful local context and route to the existing canonical owner rather than duplicate it.

• Search-language opening: the first three paragraphs naturally resolve level, subject, location, tuition/tutor intent, current stage or examination context and the page’s exact ownership role.
• One dominant reader job: a local page is a useful interface for that level × subject × location intent, not a new national subject owner.
• Educational mechanism: diagnosis → explanation → worked or observable method → deliberate practice → retrieval/variation → transfer → evidence → next decision.
• Truthful locality: use real place/travel/scheduling context only when verified; never invent a station, transport line, branch, centre or service presence. A locality title does not imply a physical eduKate branch.
• Current terminology: current-facing Secondary work uses Full SBB and SEC/G1/G2/G3 where relevant; GCE/O-Level wording remains only where historically or transitionally necessary.
• Parent decision layer: answer genuine questions about fit, class structure, diagnosis, progress evidence, workload, timing, transfer and when support should reduce or change. FAQ sections are useful when they resolve real search or decision intent, not as schema filler.
• Federated routing: English depth → SETC; Mathematics depth → BTT; Science depth → Science World; unclear cause → Yishun diagnostics; human support → Tutor System; intervention evidence → Sengkang Assessment Evidence.
• Evidence discipline: current rules, examination facts and local infrastructure claims use appropriate current sources. Internal production machinery stays outside public reader copy; public pages expose only the evidence, method, ownership and learning route readers need.

Decision states

• KEEP / PROTECT: Search Console and live-page checks support the current owner and no material factual, currentness or routing defect is present.
• HARDEN: the page’s role is sound but a useful layer such as diagnosis, FAQ, evidence, internal routing or decision support is materially weak.
• REFRESH: the role is sound but current facts, examination terminology, source references or dated interfaces have gone stale.
• REPAIR ROUTING: useful content exists, but ownership, parentage, specialist handoff, recovery route or return path is wrong or missing.
• HOLD: the page is too new or has too little finalised Search Console evidence for a ranking judgement. Structural QA may continue, but do not rewrite a strong new page merely because performance data has not matured.

Current application: the Clementi Secondary 1 Mathematics page is KEEP / PROTECT. The 27 September Bidadari English batch required a factual local-transport REPAIR and then returns to HOLD while data matures. The Amber Road Science batch received a bounded FAQ HARDEN and remains HOLD for ranking judgement. The 28 September Haig Road Science batch already passes the structural Clementi+ gate and is HOLD for ranking judgement because the available finalised Search Console window ends on 24 September 2026.

Operating rule: SEO is telemetry, not architecture. Reuse → repair → refresh → deepen → connect → build. Protect Google-selected winners, fix demonstrable defects surgically, and let new pages earn performance evidence before another branch rewrites them.

Clementi SEO+ Hub Hardening Receipt | 28 September 2026

A bounded hub-level audit applied the Clementi SEO+ floor across eduKateSingapore’s major public routing owners. The work was surgical: preserve strong live pages, remove stale or brittle state, improve the first decision route, verify internal navigation, close reciprocal owner loops and avoid creating competing hubs.

• Vocabulary: Singapore Vocabulary Guide hardened from Kindergarten through adult English and reciprocally connected to the Vocabulary Learning System and wider English estate.
• English: English Article Directory hardened as the full discovery inventory; English World and the exam-paper guide remain the subject and examination owners.
• Mathematics: Mathematics Article Directory hardened with exact live section counts, a bottleneck router and clean handoffs to Mathematics World, the Learning Library, Curriculum/Examinations and A-Math.
• Science: Science Article Directory moved from dated inventory receipts to durable routing across School Science, Science World, Inquiry, Learning Manuals, Research and examinations.
• Parent and tuition decisions: Parent Learning Support and Tuition Programmes & Locations now separate learning need, programme fit, tutor selection, cost and locality without implying unverified physical branches.
• Research and world knowledge: Research Collections, World Cities and the World Knowledge Research Library were audited for durable ownership, exact live routing and evidence/provenance handoffs.
• School learning: the Singapore Learning Library, Learning & Study Skills and Curriculum & Examination Library now expose clearer learner-state, study-method and official-source handoffs.
• Live system state: Singapore School Pathways & Calendar was reverified on 28 September 2026 against current MOE/SEAB sources for 2026 PSLE, Full SBB, 2027 SEC and the announced 2028 PSE architecture.

Result: the hardened hubs keep distinct canonical jobs but now behave as one navigable graph: question → owner → specialist/deep route → evidence or practice → return path. The current registered-route total remains 174; this receipt records maturity and routing work, not new Atlas rows.

Oral, Listening & Narrative Comprehension Maturity Wave 08 — 28 September 2026

Three canonical English examination owners have completed bounded in-place maturity passes. Existing URLs, titles, metadata, indexability, earlier teaching material and ownership boundaries were preserved. The new work adds unseen transfer, evidence control, support fade and independent self-audit rather than another generic exam-tips layer.

Status: all three remain FOUNDATION teaching owners, now materially stronger in novelty, evidence and independent execution. Further expansion should occur only when it adds a distinct capability—new transfer, diagnosis, practice or verified format guidance. Do not create duplicate generic PSLE Oral, PSLE Listening or O-Level Narrative Comprehension owners.

PSLE Comprehension Cloze Maturity Wave 08 — 28 September 2026

The apparent Comprehension Cloze route defect has been resolved without creating a replacement URL. The canonical destination PSLE Comprehension Cloze: How to Read the Blank Before the Passage is a live Jetpack Portfolio object (WP51622), which ordinary page/post inventory searches do not enumerate. Future audits must include custom post types before declaring a Portfolio route missing.

Protection receipt: PSLE Vocabulary MCQ WP139132 (~7,518 words) and PSLE Vocabulary Cloze WP139133 (~4,301 words) were audited in the same pass and deliberately left unchanged because they already meet the present capability floor. Word count alone is not a reason to reopen a healthy owner.

Status: Comprehension Cloze remains the canonical FOUNDATION owner on its established Portfolio URL, public and indexable. No duplicate owner, redirect, slug change or noindex action was required.

Secondary English Transition Maturity Wave 09 — 28 September 2026

Three canonical lower-secondary English bridge owners have completed bounded in-place maturity passes. Their URLs, titles, metadata, indexability, existing teaching material and ownership boundaries were preserved. The new work strengthens the passage from PSLE into Secondary English rather than pushing younger learners prematurely into full O-Level drilling.

Status: all three remain canonical FOUNDATION bridge owners. Their job is to make the Primary→Secondary transition more independent, evidence-aware and transferable. Future work should deepen these same URLs only when it adds genuinely new diagnosis, changed-condition transfer, practice or verified Secondary-stage guidance. Do not create generic duplicate Secondary 1 transition, lower-secondary essay-types or lower-secondary comprehension owners.

Atlas reconciliation receipt | 29 September 2026

Future Master Publish WP141190 has been reconciled against this Atlas baseline. Estates A–F remain recorded LIVE across Production Ledger I rows 1–171, and Ledger II rows 172–174 remain live Primary 4–6 Science foundation owners. These 174 inherited work records are therefore an ownership and maturity baseline, not 174 articles waiting to be commissioned. The 177 WEP identities likewise remain capability proposals resolved by owner-first action rather than a URL quota.

The twelve Stage 1 packets now have explicit current dispositions in Future Master Publish. Most resolve to CONNECT, DEEPEN, REFRESH, MATURITY or SYSTEM/REPAIR work over established owners. SING-S1-070 Household Water-Use Inquiry remains a conditional BUILD pending unpublished/federation owner checks; SING-S1-090 tutor-support review remains scope review because discovery, parent support and the Sengkang Tutor System already cover adjacent jobs.

Twelve additional reference-library briefs, SING-AUD-20260929-01–12, are registered in Future Master Publish as PROPOSED / OWNER CHECK. They concentrate on official-rule interpretation, source-to-claim fit, chart and statistics literacy, AI verification, education change tracking, curriculum-to-task translation, scientific evidence, pathway crosswalks, research abstracts, Singapore-to-world comparison and accessibility. Only distinct unresolved reader jobs should become new canonical URLs; otherwise deepen the existing owner.