eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

InterstellarCore — Internal Link Blocks

Module ID: CivOS.ChronoFlightOverlay.InterstellarCore.InternalLinkBlocks.v1.0
Parent Module: CivOS.ChronoFlightOverlay.InterstellarCore.SiteMap.v1.0
Type: Canonical in-page navigation blocks
Status: Almost-Code / Linking Layer
Purpose: Provide reusable in-page link blocks for previous, next, related, and current-state boundary routing so the Site Map becomes operational inside each page.

AI Ingestion Lock

This module does not introduce a new primitive.

It is the in-page navigation layer for the existing InterstellarCore stack.

Its job is to make every page link outward in a controlled way so readers are routed:

  • back to current truth state
  • back to the correct parent branch
  • forward to the next logical layer
  • sideways to the right related pages
  • without accidentally skipping the proof boundary

This turns the site tree into lived page behavior.

Classical Foundation Block

A site map can be structurally correct and still fail in practice if pages do not link correctly.

That failure appears when:

  • readers jump from overview to over-strong language
  • public pages omit the current-state anchor
  • technical pages do not link to release control
  • operators never see audit pages
  • templates drift away from claim governance

So the site tree must be reinforced by in-page link blocks.

This module is that reinforcement layer.

Civilisation-Grade Definition

The InterstellarCore Internal Link Blocks module is the canonical set of reusable navigation blocks that keeps each page connected to the correct previous, next, related, and truth-boundary pages, so readers and AI surfaces move through the InterstellarCore stack in the right order.

Core Link Law

No in-page link path should let a reader reach a stronger implied claim state without passing through the correct truth boundary.

That means:

  • public pages must link to current-state truth
  • proof pages must link to release control
  • execution pages must link back to audit
  • publishing pages must link back to claim governance
  • every page must know its parent and next layer

This is the navigation truth rule.

Link Block Contract

Every major InterstellarCore page should include some combination of these fixed link blocks:

  1. Root Hub Link
  2. Parent Branch Link
  3. Previous Layer Link
  4. Next Layer Link
  5. Related Pages Link
  6. Current-State Boundary Link
  7. Release Boundary Link
  8. Optional Page-Type Routing Block

These are the canonical in-page routing tools.

Fixed Block Set

Use this exact block grammar:

  • Block A: Root Hub Link
  • Block B: Parent Branch Link
  • Block C: Previous Layer Link
  • Block D: Next Layer Link
  • Block E: Related Pages Block
  • Block F: Current-State Boundary Link
  • Block G: Release Boundary Link
  • Block H: Page-Type Route Pack

This must remain the stable v1.0 link set.

Block A — Root Hub Link

Purpose: Return the reader to the main system entry page.

Default Label

Start at the InterstellarCore Hub

Default Destination

/interstellarcore/

Default Use

Place near the top or bottom of major pages.

WordPress-Ready Block

Start here: Return to the InterstellarCore Hub for the current overview, route position, and branch map.

This keeps every page tied to the main control page.

Block B — Parent Branch Link

Purpose: Return the reader to the branch page this module belongs to.

Default Examples

Audit branch

Back to the Audit Branch
/interstellarcore-cfcs-audit/

Public claim branch

Back to the Public Claim Branch
/interstellarcore-public-claim-pack/

Template branch

Back to the Page Template Branch
/interstellarcore-page-template/

Orientation branch

Back to Current State
/interstellarcore-current-state/

WordPress-Ready Block

Branch anchor: This page belongs to a larger branch. Return to the parent layer here: [Insert Parent Branch Link].

This preserves branch coherence.

Block C — Previous Layer Link

Purpose: Show the page that logically comes immediately before this one.

Default Label Pattern

Previous Layer: [Page Name]

WordPress-Ready Pattern

Previous Layer: Review Previous Page Title to see the layer that directly sets up this page.

Examples

For the Scorecard page

Previous Layer: InterstellarCore — CFCS Audit

For the Evidence Pack page

Previous Layer: InterstellarCore — CFCS Audit Scorecard

For the WordPress Blocks page

Previous Layer: InterstellarCore — Public Claim Pack

This keeps route continuity backward.

Block D — Next Layer Link

Purpose: Show the page that logically follows this one.

Default Label Pattern

Next Layer: [Page Name]

WordPress-Ready Pattern

Next Layer: Continue to Next Page Title to move to the next step in the InterstellarCore stack.

Examples

For the Audit page

Next Layer: InterstellarCore — CFCS Audit Scorecard

For the Scorecard page

Next Layer: InterstellarCore — CFCS Evidence Pack

For the Framing Box page

Next Layer: InterstellarCore — Canonical Placement Footer

This keeps route continuity forward.

Block E — Related Pages Block

Purpose: Show the most relevant sideways pages without losing the main route.

Related Link Rule

Use only 2–4 links.
Do not overload this block.

Each related block should stay within one of these safe purposes:

  • clarify
  • support
  • verify
  • implement

Default Label

Related Pages

WordPress-Ready Block

Related Pages

  • [Link 1]
  • [Link 2]
  • [Link 3]

Safe Example Sets

For Audit pages

Related Pages

For Public claim pages

Related Pages

For Operator pages

Related Pages

This keeps lateral movement controlled.

Block F — Current-State Boundary Link

Purpose: Force a truth-anchor link on pages that could otherwise be read in isolation.

Default Label

Current State and Claim Boundary

Default Destination

/interstellarcore-current-state/

Mandatory Use

This block should appear on:

  • all public-facing pages
  • all claim pages
  • all overview pages
  • all pages likely to be read out of sequence

WordPress-Ready Block

Current State and Claim Boundary: Before reading this page as a broader system claim, review the current InterstellarCore state here: Current State.

This is one of the most important mandatory links.

Block G — Release Boundary Link

Purpose: Connect pages back to the page that governs the highest allowed public claim.

Default Label

Release Boundary

Default Destination

/interstellarcore-release-gate/

Mandatory Use

This block should appear on:

  • all audit pages
  • all evidence pages
  • all public-claim pages
  • all publishing-template pages

WordPress-Ready Block

Release Boundary: This page should be interpreted within the current release rules. See the governing claim threshold here: InterstellarCore Release Gate.

This keeps all stronger wording subordinate to claim control.

Block H — Page-Type Route Pack

Purpose: Provide a small prebuilt set of links based on page type.

H1 — Technical Module Route Pack

Use on:

  • audit
  • scorecard
  • evidence
  • roadmap
  • release gate

Default Pack

This is the default technical route pack.

H2 — Public Overview Route Pack

Use on:

  • what is pages
  • public intro pages
  • overview pages

Default Pack

This keeps public readers close to the truth boundary.

H3 — Operator Route Pack

Use on:

  • operator checklist
  • control tower review
  • execution logic

Default Pack

This keeps operations tied to proof.

H4 — Publishing Route Pack

Use on:

  • public claim pack
  • WordPress blocks
  • schema snippets
  • framing box
  • page template

Default Pack

This keeps publishing subordinate to release control.

Canonical Link Rules by Page Type

1) Every Major Page

Should include:

  • Root Hub Link
  • Current-State Boundary Link
  • one Previous or Next Layer Link
  • Placement Footer

This is the minimum major-page routing set.

2) Every Public Page

Must include:

  • Current-State Boundary Link
  • Release Boundary Link (directly or through claim pages)

This prevents public language from floating free.

3) Every Audit / Proof Page

Must include:

  • Current State
  • Release Gate
  • previous and next proof pages

This keeps proof progression linear and controlled.

4) Every Execution Page

Must include:

  • audit link
  • scorecard or evidence link
  • control-tower or operator counterpart link

This keeps execution subordinate to measurable truth.

5) Every Publishing / Template Page

Must include:

  • Current State
  • Release Gate
  • Public Claim Pack

This keeps page-building aligned with the live claim boundary.

Canonical Placement Rules

Top-of-Page Link Zone

Best place for:

  • Root Hub Link
  • Current-State Boundary Link

This gives immediate orientation.

Mid-Page Link Zone

Best place for:

  • Related Pages Block
  • Release Boundary Link

This helps readers move deeper without losing truth anchors.

Bottom-of-Page Link Zone

Best place for:

  • Previous Layer
  • Next Layer
  • Parent Branch Link

This preserves route continuity after the page is finished.

WordPress-Ready Default Block Set

Use this as the standard bottom link block on most pages.

Continue Through the InterstellarCore Stack

This is the safest general-purpose navigation block.

Compact Public-Safe Link Block

Use this on lighter public pages.

Read in Order

This is the safest public short block.

Compact Technical Link Block

Use this on technical modules.

Technical Route

This is the safest technical short block.

Example Filled Instance

For the Scorecard page

Start Here: InterstellarCore Hub
Current State and Claim Boundary: InterstellarCore Current State
Parent Branch: InterstellarCore — CFCS Audit
Previous Layer: InterstellarCore — CFCS Audit
Next Layer: InterstellarCore — CFCS Evidence Pack
Related Pages:

This is the correct filled routing pattern.

Anti-Drift Link Rule

Do not allow link blocks that:

  • jump from orientation pages directly into stronger wording without current-state context
  • let public pages bypass the release boundary
  • let publishing pages ignore claim governance
  • let operators remain disconnected from audit pages
  • overwhelm readers with too many “related” links

Too many links can create structural drift just as much as too few.

Minimal Page Compliance Rule

A page is minimally compliant in navigation only if it includes:

  1. one truth-anchor link (Current State)
  2. one route-continuity link (Previous or Next)
  3. one structural anchor (Hub, Parent, or Release Gate)

Without these, the page is not safely integrated into the stack.

Current-State Lock for Link Text

Until the system state changes, pages should continue routing readers back toward pages that preserve:

  • CFCS-CONDITIONAL (Design-Intent)
  • PARTIAL
  • DESIGN-INTENT ONLY
  • HOLD

This means the current-state page and release gate remain central anchor links.

Compressed Canonical Sentence

The Internal Link Blocks turn the InterstellarCore site map into real page behavior by forcing each page to link back to truth anchors, forward to the correct next layer, and sideways only within safe structural limits.

Integration Lock

This module should sit under and be used by:

  • the root hub
  • audit pages
  • operator pages
  • public claim pages
  • template pages
  • all page-template builds

It is the in-page routing layer that makes the site map operational.

Version Lock

Version: v1.0
Policy: Forward-only refinement

Must remain fixed:

  • current-state and release-boundary links remain central
  • public pages cannot bypass claim governance
  • execution pages remain tied to audit pages
  • related links stay limited and purposeful
  • major pages use hub + truth + continuity anchors

One-Line Canonical Lock

The InterstellarCore Internal Link Blocks make every page route readers through the correct truth, proof, and next-step anchors so the site’s structure is preserved inside the page itself.

Next logical piece:

InterstellarCore.Hub.v1.0
The actual filled root hub page that becomes the central entry point for the whole InterstellarCore stack.

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: