IMPLEMENTATION MAP · Version 1.1 · October 13, 2026
Now published: an explorable information world
The connected directory and website atlas now link world guides, learning resources, stakeholder information, books, music, research, partners, and support. Visitors can enter the relevant page and continue through related destinations without returning to the homepage. This is an information architecture, not a new live 3D application or student portal.
The content foundation
New Shopify page records carry a stable destination ID and release value. These help identify content independently of its display title. A published record, an approved school lesson, and a verified game launch target remain separate records with separate evidence.
Separate systems of record
Shopify: public content, product catalog, and actual merchandise orders. Project control tower: tasks, approval records, and build evidence. Game platform: gameplay and verified virtual entitlements. District systems: identity, rosters, learning records, and restricted assessments. Code repository: versioned implementation and appropriately sanitized release evidence. One system must not silently substitute for another.
Planned publication pipeline
Authorized editor → appropriate review → approved content version → authenticated event receiver → durable queue → authoritative source check → public-field filter → permitted website adapters and cache. An event asks for synchronization; it is not approval to publish.
Proposed API boundary
Public read routes would expose approved titles, summaries, related destinations, content notes, canonical URLs, version dates, and status. Administrative synchronization routes would be authenticated and server-side. Student records, answer keys, customer/order details, private tasks, and secrets are excluded from the public service.
Reliability requirements
Verify provider signatures against the original request body; allow only registered sources and topics; persist duplicate detection; refetch authoritative records; prevent stale versions overwriting current content; handle retries, failed-event review, revocation, reconciliation, and rollback. Reference: Shopify webhook verification documentation. These are implementation requirements, not a deployed-service claim.
Start small and scale deliberately
The connected store is on Shopify Basic; this release makes no plan change. Additional content pages do not themselves justify an enterprise upgrade. Staff access, storefront entitlements, automation features, measured API demand, and commercial requirements should drive a separate tier decision. Reference: Shopify's current plan comparison.
Not activated by this release
Production integration hosting, credentials, webhook subscriptions, multi-site synchronization, school authentication, and real student enrollment. The custom homepage navigation needs separate integration into its existing layout. Shared-menu configuration does not replace that code automatically.
Commerce boundary
Physical merchandise and Roblox virtual purchases remain distinct. Use only an official, eligible integration and verified fulfillment. School mode must have no purchase prompts, paid skips, advertising, donations, token offers, or financial rewards. See the commerce guide.
DOCUMENT ADDENDUM 1.2 · October 14, 2026 · Public information and proposals
Propagate approved content by audience
The stakeholder update uses existing public page destinations and direct links. Future synchronization should carry the approved source version, audience and publication date; changes to student, family and administrator information should be reconciled together. Restricted staff annexes, assessment keys and private research records must remain outside public adapters.
The proposed review cadence is an editorial plan, not an activated publishing job or data-collection service.
Student guide · Family consultations · Administrator update · Research record · Current readiness