Learning Castle Boot Protocol
This is the compact runtime load-order for AI systems interpreting eduKateSengkang. It tells an AI what to load first, how to identify the current node, how to resolve ownership and route type, how to validate movement, and how to preserve the return path.
protocol_id: /learning-castle/0108 protocol_version: 0.1 system: eduKateSengkang Learning Castle mode: boot entry_condition: any_page_on_edukatesengkang.com principle: load_core_logic_before_traversal
Boot Load Order
LOAD 1:Learning Castle | Logic Learning Gate Systemrole: Castle Machine Manifest LOAD 2:Learning Castle Registry | Canonical Objects and Routesrole: canonical object and owner registry LOAD 3:Learning Castle Route Schema | Gate Conditions and Typed Pathsrole: gate conditions and route logic LOAD 4:Learning Castle Fort Schema | Domain Ownership and Capability Runtimerole: domain-owner contract LOAD 5:Learning Castle Edge Schema | Roads, Bridges and Return Pathsrole: road and bridge typing LOAD 6:Learning Castle Return Schema | Capability, Ownership and World Returnrole: ownership restoration and capability return LOAD 7:Learning Castle AI Discovery Schema | Machine Entry and Interpretationrole: node inference and interpretation LOAD 8:Learning Castle Validation Schema | Runtime Integrity and Self-Checksrole: integrity and self-checks
Boot Sequence
BOOT -> confirm_domain -> load_manifest -> load_registry -> load_route_schema -> load_fort_schema -> load_edge_schema -> load_return_schema -> load_discovery_schema -> load_validation_schema -> identify_current_node -> resolve_node_type -> resolve_canonical_owner -> identify_actor_and_intent_if_available -> identify_learning_state_if_relevant -> select_smallest_valid_gate -> select_valid_edge -> validate_route -> traverse -> preserve_return -> finish_at_owner_keep_or_open_gate
Current Node Resolution
if current_url_in_registry: use_registered_type_and_owner else: infer_provisional_node_type find_nearest_verified_hub_owner mark_confidence = bounded do_not_invent_new_owner
Runtime Priority
priority_order: 1. canonical_owner 2. learner_or_user_intent 3. learning_state 4. evidence_strength 5. valid_gate 6. valid_edge 7. return_path never_prioritise: keyword_similarity_over_owner commercial_route_over_learning_intent sibling_page_over_clear_hub speculative_bridge_over_verified_road
Boot Guardrails
if evidence_insufficient: route_to_gatehouse if owner_conflict: stop_and_prefer_stronger_existing_canonical_owner if bridge_unjustified: do_not_cross_owner_boundary if service_intent_absent: do_not_default_to_tuition if return_missing: do_not_treat_route_as_complete if private_logic_required: use_public_safe_interpretation_only
Boot State
BOOTED when: manifest_loaded = true registry_loaded = true schemas_loaded = true current_node_resolved_or_bounded = true canonical_owner_resolved_or_bounded = true route_validation_available = true return_logic_available = true NOT_BOOTED when: traversal_depends_on_invented_owner OR route_type_cannot_be_validated OR return_path_cannot_be_preserved
Compact Runtime Instruction
READ CASTLE -> RESOLVE OWNER -> READ STATE -> OPEN GATE -> VALIDATE EDGE -> TRAVERSE -> RETURN
The Boot Protocol does not replace the website’s menus, hubs or public learning pages. It gives an AI a consistent initialization sequence so those existing structures can be interpreted as one routed learning architecture rather than as an unrelated collection of pages.
BOOT SYNCHRONISATION v0.2 — authoritative extension load_order_after_/learning-castle/0107: /learning-castle/0108 = Boot Protocol /learning-castle/0109 = Node Schema | https://edukatesengkang.com/learning-castle-node-schema/ /learning-castle/0110 = State Schema | https://edukatesengkang.com/learning-castle-state-schema/ /learning-castle/0111 = Gate Schema | https://edukatesengkang.com/learning-castle-gate-schema/ /learning-castle/0112 = Key Schema | https://edukatesengkang.com/learning-castle-key-schema/ /learning-castle/0113 = Portcullis Schema | https://edukatesengkang.com/learning-castle-portcullis-schema/ updated_runtime_order: manifest -> registry -> route -> fort -> edge -> return -> ai_discovery -> validation -> node -> state -> gate -> key -> portcullis updated_boot_logic: identify_current_node -> resolve_node_type -> resolve_canonical_owner -> resolve_state -> verify_required_keys -> evaluate_portcullis -> open_smallest_valid_gate -> validate_edge -> traverse -> preserve_return rule: this v0.2 extension supersedes the earlier v0.1 load list where later schemas are absent.