Stage 1 · eduKateAI | Future Master Publish · 26 September 2026. This is the publishing register for eduKateAI / Orchard: human reception, resolving which owner can help, explicit handoffs and useful returns. It does not replace the existing routing pages or imply that an AI tutoring application is deployed.
Register: FMP-S1-ORCHARD-000 · source link corrected 26 September 2026. Baseline: fourteen existing page records, WEP170 and eight route-completion packets: 23 work records, not 23 new articles. Sources: the published Orchard inventory, Eight-Wing Ecosystem Runtime and Ecosystem Atlas. Active federation publishing controls. The former education directive on WahLiao is not a governing dependency. WEP170 retains its historical ID and bounded working job below. This page, WP17346, is the active register; duplicate WP17347 is an inactive draft and its differently numbered packet meanings must not replace this queue.
Existing owners · White Paper allocation · First packets. State begins SOURCE-LINKED / MATURITY REVIEW for existing pages and REGISTERED / OWNER CHECK for proposals. The inventory identifies destinations, not a fresh evaluation of every page or service.
Publishing and routing contract
Record task ID, source ID, precise reader job, canonical owner and actual WordPress ID, parent, input needed, handoff destination, reason for the handoff, expected return, action, priority, release state and check date. REUSE, DEEPEN, CONNECT and REFRESH precede BUILD. HOLD unresolved expertise, evidence, privacy or ownership. Publication stages are REGISTERED → OWNER RESOLVED → DRAFT → REVIEWED → PUBLISHED / STORE CHECKED → PUBLIC VERIFIED → ROUTE VERIFIED. Learning effects need a separate evaluation.
Orchard routes uncertainty; it does not absorb English, Mathematics, public knowledge, recovery or professional tutoring. The seven substantive education registers remain responsible for their content. The working graph is question → sufficient context → exact owner → bounded task → result → next decision. A handoff is useful when the reader knows why to go, what to take, what to bring back and when the job is complete.
Federation Publish Gate v1.1
Desk: FED.WING.ORCHARD. Before any task moves to BUILD, it must pass the federation gate below. Search demand can trigger inspection; it cannot bypass ownership.
- Reader-job test. State the exact human job in one sentence. If the job is vague, HOLD.
- Owner test. Search the live estate and Ecosystem Atlas. Prefer REUSE → DEEPEN → CONNECT → REFRESH before BUILD.
- 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.
- Lifecycle test. Record PLANNED, CANONICAL LIVE, SUPPORTING LIVE, CURRENT UPDATE, SUPERSEDED, HISTORICAL, REPAIR REQUIRED or RETIRED.
- 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.
- 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.
- Freshness test. Assign F0 STABLE, F1 INSTITUTIONAL, F2 LOCAL/PROGRAMME, F3 CURRENT RULE, F4 EVENT/LIVE or FH HISTORICAL and identify the review trigger.
- Evidence test. Separate durable mechanism from changing fact; choose the appropriate source class and expose uncertainty where precision is not justified.
- 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.
- 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.
- 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.
- Release-receipt test. If ownership, meaning, current rules or major crosswalks change, create a change receipt and recheck dependent routes.
Wing-specific boundary: Orchard may BUILD only a genuine reception, owner-resolution, routing or return-path job. It must not absorb the subject, public-reference, learner-runtime, recovery or local-implementation work it routes to.
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.
Fourteen existing owner records
Default action is REUSE / CONNECT. The homepage record is a protected dependency, not authorisation to edit the homepage. Verify changing financial, legal, health or official-system information with the responsible source when revising those routes. Do not publish personal details or infer an individual diagnosis.
| Task / WP ID | Existing page | Work to inspect |
|---|---|---|
| OR001 / 16860 | What Is eduKateAI? | Protected homepage dependency; no edit in this release. |
| OR002 / 16861 | How eduKateAI Routes a Question | P1; sufficient context, explicit destination and return. |
| OR003 / 16862 | The eduKate Learning Ecosystem | P1; one clear job per estate; preserve established handoffs. |
| OR004 / 16874 | How eduKateAI Should Behave | P1; human-centred scope and truthful service status. |
| OR005 / 17018 | Eight Registered Wings, One Federated Programme | P1; current owner record; no extra competing master map. |
| OR006 / 17031 | How to Route an Education | P1; education stage → present need → specialist → return. |
| OR007 / 17033 | How to Route Money Through a Family | P3; route purpose and responsible expertise, not personalised financial recommendations. |
| OR008 / 17035 | How to Route Intelligence | P2; locate the next piece of thinking without replacing human judgement. |
| OR009 / 17037 | How to Route a Life Across Two Generations | P2; responsibilities and capability transfer; no private family assumptions. |
| OR010 / 17041 | How to Route a Family in Society | P2; institutions and actual family constraints. |
| OR011 / 17044 | How to Route a School Problem | P1; separate learning, communication, relationships and official school decisions. |
| OR012 / 17047 | How to Route a Weak Result | P1; Sengkang evidence versus Yishun recovery; no repeated diagnosis. |
| OR013 / 17051 | How to Route a Career | P2; eduKateSG ongoing development versus Yishun conversion. |
| OR014 / 17056 | How to Route Risk | P3; bounded uncertainty and appropriate responsible help. |
White Paper allocation
| Source | Working job | Action and boundary |
|---|---|---|
| WEP170 | eduKateAI: What Exists, How Questions Are Routed and How Learners Return | P1 REUSE OR002–005. Correct the historical assumption that an explanatory page establishes a deployed diagnosis/practice runtime. Public AI literacy belongs to eduKateSingapore, educational AI use to Sengkang, subject validation to the specialists, and system explanation to eduKateSG. Do not publish another general eduKateAI root. |
Eight Stage 1 route packets
Each packet is REGISTERED. P1 means first-route work, not a scheduled promise. These packets can be completed by improving existing routes rather than creating eight articles.
| ID | Route to complete | Acceptance condition |
|---|---|---|
| OR-S1-010 | I Do Not Know Which Site I Need | OR002/003 resolve a job to a named maintained owner, not an indiscriminate link list. |
| OR-S1-020 | A Weak Result: More Practice or a Recovery Plan? | OR012 → Sengkang evidence or Yishun recovery → one next action. |
| OR-S1-030 | English or Mathematics in a Word-Problem Difficulty? | OR011 → Sengkang task evidence → BTT or SETC → fresh problem. |
| OR-S1-040 | Choosing a Tutor and Returning With Evidence | Public discovery → Tutor System → subject/local teaching → review decision. |
| OR-S1-050 | A Punggol Family Constraint Without a New Curriculum | OR010 → Punggol local owner → original learning task. |
| OR-S1-060 | Adult Learning or Career Rebuilding? | OR013 → eduKateSG Career & Adulthood or Yishun conversion → work evidence. |
| OR-S1-070 | A Question That Needs Another Responsible Professional | State the limit and appropriate handoff; do not continue a tutoring workflow into diagnosis or emergency advice. |
| OR-S1-080 | Return From an Inquiry With Something Usable | Public project → Science/Mathematics/English/inquiry owners → limited, inspectable result → next question. |
Upgrade responsibilities and release
Lead U18 job-based owner resolution and U20 symptom-to-owner routing coordination. Participate in U22 only as a bounded reception/routing layer after the actual service has been reviewed. Keep ordinary text routes useful without an account or AI interaction. U27 privacy and U41 accessibility are release dependencies for any new service.
Before work, claim the task and inspect the latest owner. Before saving, check exact destinations and avoid overwriting a newer edit. After saving, read the stored content and public page; record public verification separately from route and learner evaluation. This register changes no homepage, menu, theme, proprietary runtime record or existing article body. WahLiao remains a separate estate and is not turned into another education wing.
