Breadcrumb Philosophy: Difference between revisions
No edit summary |
Structural pre-cal only. Fixed param name, added inline option comments, added missing mandatory templates, made Resource visible (removed display:none), corrected template order. Nonconformances logged first. Content calibration still pending. |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Development Notice | |||
|status = Active Development | |||
}} | |||
= Breadcrumb Philosophy = | = Breadcrumb Philosophy = | ||
'''Calibration is not only about recording what we know. It is also about making visible what we deliberately do not yet know, why, and what evidence would change that.''' Everything below follows from that principle. | '''Calibration is not only about recording what we know. It is also about making visible what we deliberately do not yet know, why, and what evidence would change that.''' Everything below follows from that principle. | ||
{{GameModule | {{GameModule | ||
| type = Meta & Framework | | type = Meta & Framework <!-- options: Meta & Framework, Core Diagnostic, Builder & Sovereignty, Calibration & Accountability, Practical Application, Sovereign Strategies, Strategic Actionable Plans, Hidden Mastery, Framework Guidelines --> | ||
| category = [[:Category:Meta & Framework|Meta & Framework]] | | category = [[:Category:Meta & Framework|Meta & Framework]] <!-- must match an existing Category page --> | ||
| Functional Layer | | Calibration Type = Governance <!-- displays as Functional Layer. options: Governance, Diagnostic Layer, Builder Layer, Calibration Layer, Application Layer, Strategic Layer, Framework Infrastructure, Maintenance --> | ||
| Application Layer = Framework Infrastructure | | Application Layer = Framework Infrastructure <!-- options: Multi-Layer, Framework Infrastructure, Individual, Institutional --> | ||
| Version = 0.1 | | Version = 0.1 | ||
| Maturity = Development | | Maturity = Development <!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate --> | ||
| Last Updated = 2026-07- | | Last Updated = 2026-07-20 <!-- static only. Must match review_date. FORBIDDEN: magic words --> | ||
| description = Defines the Breadcrumb Philosophy — when, why, and how to leave explicit open-items, notes, and trigger conditions inside developing pages so future calibrators can find and act on them. | | description = Defines the Breadcrumb Philosophy — when, why, and how to leave explicit open-items, notes, and trigger conditions inside developing pages so future calibrators can find and act on them. | ||
}} | }} | ||
== What a Breadcrumb Is == | == What a Breadcrumb Is == | ||
A '''breadcrumb''' is an explicit, visible note left inside a page marking something '''deliberately unresolved''' — an open question, a known gap, a provisional decision, or a condition under which something should be revisited. It is not a bug or a sign of incompleteness to be ashamed of. It is a stated, findable trail for whoever calibrates the page next. | A '''breadcrumb''' is an explicit, visible note left inside a page marking something '''deliberately unresolved''' — an open question, a known gap, a provisional decision, or a condition under which something should be revisited. It is not a bug or a sign of incompleteness to be ashamed of. It is a stated, findable trail for whoever calibrates the page next. | ||
| Line 24: | Line 24: | ||
== Why This Matters == | == Why This Matters == | ||
Without breadcrumbs, a future calibrator who hits an unstated assumption has only two options: reverse-engineer the original reasoning from scratch (slow, and often impossible if the original discussion isn't preserved anywhere), or guess — and a guess risks silently overwriting something that was actually a deliberate, considered choice. Breadcrumbs turn that failure mode into a solvable task instead of a mystery. | Without breadcrumbs, a future calibrator who hits an unstated assumption has only two options: reverse-engineer the original reasoning from scratch (slow, and often impossible if the original discussion isn't preserved anywhere), or guess — and a guess risks silently overwriting something that was actually a deliberate, considered choice. Breadcrumbs turn that failure mode into a solvable task instead of a mystery. | ||
| Line 30: | Line 29: | ||
== Types of Breadcrumbs == | == Types of Breadcrumbs == | ||
Not all breadcrumbs resolve the same way: | Not all breadcrumbs resolve the same way: | ||
| Line 36: | Line 34: | ||
* '''Temporary breadcrumbs''' — open items expected to resolve eventually, but without a precisely stated trigger yet (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience"). | * '''Temporary breadcrumbs''' — open items expected to resolve eventually, but without a precisely stated trigger yet (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience"). | ||
* '''Trigger breadcrumbs''' — open items with an explicit, stated condition that retires them automatically once met (e.g. "open until three independent calibration reports exist"). Once the condition is satisfied, the breadcrumb should be removed or marked resolved — leaving it in place past its trigger is itself a form of drift. | * '''Trigger breadcrumbs''' — open items with an explicit, stated condition that retires them automatically once met (e.g. "open until three independent calibration reports exist"). Once the condition is satisfied, the breadcrumb should be removed or marked resolved — leaving it in place past its trigger is itself a form of drift. | ||
== When to Use a Breadcrumb == | == When to Use a Breadcrumb == | ||
Leave a breadcrumb when: | |||
* A decision was deliberately deferred, not forgotten (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience"). | * A decision was deliberately deferred, not forgotten (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience"). | ||
* A rule or number is provisional and expected to be revisited under specific conditions (e.g. a threshold that should change once real cases test it). | * A rule or number is provisional and expected to be revisited under specific conditions (e.g. a threshold that should change once real cases test it). | ||
| Line 48: | Line 45: | ||
== When Not to Use a Breadcrumb == | == When Not to Use a Breadcrumb == | ||
Breadcrumbs lose their value if overused. Do not leave a breadcrumb for: | |||
* Something that's simply finished and correct — a completed section doesn't need a note saying "this is done." | * Something that's simply finished and correct — a completed section doesn't need a note saying "this is done." | ||
* Vague unease without a specific, nameable gap. "This might need work later" is not a breadcrumb; it's noise. A real breadcrumb names the specific open question, not just a feeling that something's unfinished. | * Vague unease without a specific, nameable gap. "This might need work later" is not a breadcrumb; it's noise. A real breadcrumb names the specific open question, not just a feeling that something's unfinished. | ||
| Line 58: | Line 55: | ||
== How to Write a Good Breadcrumb == | == How to Write a Good Breadcrumb == | ||
A good breadcrumb has three parts, though not always in this exact order: | A good breadcrumb has three parts, though not always in this exact order: | ||
| Line 70: | Line 66: | ||
== Self-Enforcing Breadcrumbs == | == Self-Enforcing Breadcrumbs == | ||
The strongest breadcrumbs make their own neglect visible. A basic breadcrumb just states an open item. A self-enforcing breadcrumb states what it would mean if the breadcrumb itself quietly disappeared without being resolved — turning silent removal into a flaggable Reality Override pattern rather than a clean, invisible edit. | The strongest breadcrumbs make their own neglect visible. A basic breadcrumb just states an open item. A self-enforcing breadcrumb states what it would mean if the breadcrumb itself quietly disappeared without being resolved — turning silent removal into a flaggable Reality Override pattern rather than a clean, invisible edit. | ||
| Line 78: | Line 73: | ||
== Relationship to Other Mechanisms == | == Relationship to Other Mechanisms == | ||
'''Unlike Calibration Reports or Decision Records, breadcrumbs are forward-looking rather than historical.''' They identify unfinished calibration work rather than documenting completed calibration work — which is why they live inside the page itself, at the point of the open question, rather than in a log or report. | '''Unlike Calibration Reports or Decision Records, breadcrumbs are forward-looking rather than historical.''' They identify unfinished calibration work rather than documenting completed calibration work — which is why they live inside the page itself, at the point of the open question, rather than in a log or report. | ||
Breadcrumbs are not a replacement for the project's other tracking tools — they're the connective tissue between them: | Breadcrumbs are not a replacement for the project's other tracking tools — they're the connective tissue between them: | ||
* '''Admin Page Status fields''' (`drift_report_status`, `calibration_rationale`) track a page's structured metadata state. | * '''Admin Page Status fields''' (`drift_report_status`, `calibration_rationale`) track a page's structured metadata state. | ||
* '''Calibration Reports''' (Talk page) track the history of what changed and why, over time. | * '''Calibration Reports''' (Talk page) track the history of what changed and why, over time. | ||
| Line 88: | Line 83: | ||
== Tech Insight == | == Tech Insight == | ||
'''Breadcrumbs are a mindset before they are a mechanism.''' The underlying shift is refusing rigidity as a condition for progress — the belief that a page (or a system, or a decision) must be perfected before it can be built on is what actually stalls development, not incompleteness itself. Once "unresolved" is treated as a normal, visible, findable state rather than a failure to hide, it becomes possible to build forward '''and''' continue shaping the foundation at the same time, instead of being stuck waiting for a finished state that never arrives. | '''Breadcrumbs are a mindset before they are a mechanism.''' The underlying shift is refusing rigidity as a condition for progress — the belief that a page (or a system, or a decision) must be perfected before it can be built on is what actually stalls development, not incompleteness itself. Once "unresolved" is treated as a normal, visible, findable state rather than a failure to hide, it becomes possible to build forward '''and''' continue shaping the foundation at the same time, instead of being stuck waiting for a finished state that never arrives. | ||
This is the same insight underneath [[Permanent Beta]] and [[Reality Override Game]], applied specifically to the moment of '''building''' rather than the moment of '''defending''' an existing model. Where Reality Override Game asks "will you update when reality disagrees," this insight asks the earlier question: "will you let yourself start before everything is certain, and trust the update mechanism to catch what you got wrong." Recognizing this mindset elsewhere — anywhere a builder is stuck waiting for permission to be imperfect — is the actual transferable value of this page, beyond its specific mechanism. | This is the same insight underneath [[Permanent Beta]] and [[Reality Override Game]], applied specifically to the moment of '''building''' rather than the moment of '''defending''' an existing model. Where Reality Override Game asks "will you update when reality disagrees," this insight asks the earlier question: "will you let yourself start before everything is certain, and trust the update mechanism to catch what you got wrong." Recognizing this mindset elsewhere — anywhere a builder is stuck waiting for permission to be imperfect — is the actual transferable value of this page, beyond its specific mechanism. | ||
'''See the Game. Refuse the Game. Build Better.''' | |||
{{RelatedPages}} | |||
{{Standalone Transparency}} | {{Standalone Transparency}} | ||
{{Calibration Dependent}} | {{Calibration Dependent}} | ||
{{Calibration Dependencies Display}} | {{Calibration Dependencies Display}} | ||
{{Calibration Maintenance}} | |||
{{Framework Reference}} | |||
{{Calibration Procedure Reference}} | |||
{{Tracking Logs Reference}} | |||
[[Category:Meta & Framework]] | [[Category:Meta & Framework]] | ||
[[Category:Site Maintenance]] | [[Category:Site Maintenance]] | ||
{{Resource | {{Resource | ||
| Title = Breadcrumb Philosophy | | Title = Breadcrumb Philosophy | ||
| Line 110: | Line 107: | ||
| Category = Meta & Framework | | Category = Meta & Framework | ||
}} | }} | ||
{{Admin Page Status | {{Admin Page Status | ||
<!-- Do Not Remove commented out Reference Options --> | |||
<!-- === CORE STATUS === --> | |||
<!-- options: Done, Needs review, Not started --> | |||
| categorization = Done | | categorization = Done | ||
<!-- options: Self-Assessment, Confirmed Rating --> | |||
| calibration_review = Self-Assessment | | calibration_review = Self-Assessment | ||
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate --> | |||
| instrument_grade = Development | | instrument_grade = Development | ||
<!-- options: Low, Moderate, High --> | |||
| validation = Low | | validation = Low | ||
| calibration_rationale = | | calibration_rationale = Structural pre-cal only. Fixed param name (Calibration Type), added required inline option comments, added the four missing mandatory templates, made Resource visible (removed display:none), and corrected template order. Content calibration not performed. | ||
| review_confidence = Moderate | | review_confidence = Moderate <!-- options: High, Moderate, Low --> | ||
| review_date = 2026-07- | | review_date = 2026-07-20 <!-- static only. Must match Last Updated --> | ||
| reviewed_by = Sovereign | | reviewed_by = Sovereign | ||
<!-- options: Core, Supporting, Peripheral --> | |||
| priority = Core | | priority = Core | ||
| review_threshold = 60 | | review_threshold = 60 | ||
<!-- options: Yes, No, Not checked --> | |||
| has_backlinks = Not checked | | has_backlinks = Not checked | ||
<!-- options: Yes, Has red links, No, Not checked --> | |||
| outbound_links_valid = Not checked | | outbound_links_valid = Not checked | ||
<!-- options: Yes, No --> | |||
| in_outline = No | | in_outline = No | ||
<!-- options: Yes, No --> | |||
| in_category_outline = No | | in_category_outline = No | ||
<!-- options: Done, Needs review, Not started --> | |||
| templates_complete = Done | | templates_complete = Done | ||
<!-- options: Meets standard, Needs work, Not checked --> | |||
| formatting_standard = Meets standard | | formatting_standard = Meets standard | ||
<!-- options: Applied, Not applicable, Needs work --> | |||
| symmetry_check = Not applicable | | symmetry_check = Not applicable | ||
<!-- options: Yes, No, Not applicable --> | |||
| self_report_flagged = No | | self_report_flagged = No | ||
<!-- options: Yes, Needs work, Not checked --> | |||
| terminology_consistent = Yes | | terminology_consistent = Yes | ||
<!-- options: Confirmed by other party, Self-assessed only --> | |||
| standing_check = Self-assessed only | | standing_check = Self-assessed only | ||
<!-- options (multiple allowed, semicolon-separated): Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open. "None open" valid ONLY alone. --> | |||
| drift_report_status = None open | | drift_report_status = None open | ||
| depends_on = Reality Override Game | | depends_on = Reality Override Game | ||
}} | }} | ||
Latest revision as of 09:51, 20 July 2026
Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.
- Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.
|
CYCLE Calibration position Status — Active Development
This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute. |
Breadcrumb Philosophy
Calibration is not only about recording what we know. It is also about making visible what we deliberately do not yet know, why, and what evidence would change that. Everything below follows from that principle.
Meta
Breadcrumb Philosophy
| Type | Meta & Framework |
|---|---|
| Functional Layer | Governance |
| Application Layer | Framework Infrastructure |
| Category | Meta & Framework |
| Version | 0.1 |
| Maturity | Development |
| Last Calibration | 2026-07-20 |
| Status | Permanent Beta |
| Description | Defines the Breadcrumb Philosophy — when, why, and how to leave explicit open-items, notes, and trigger conditions inside developing pages so future calibrators can find and act on them. |
Menu
Core Principles
- Reality gets final vote
- See the Game. Refuse the Game. Build Better.
- Permanent Beta
Navigation
Related
What a Breadcrumb Is
A breadcrumb is an explicit, visible note left inside a page marking something deliberately unresolved — an open question, a known gap, a provisional decision, or a condition under which something should be revisited. It is not a bug or a sign of incompleteness to be ashamed of. It is a stated, findable trail for whoever calibrates the page next.
A breadcrumb is different from silence. A page that simply doesn't mention an unresolved issue looks the same, to a future reader, as a page that resolved that issue and moved on — absence of evidence is ambiguous between "nobody thought about it" and "everybody thought about it and resolved it." A breadcrumb separates those two cases, which are otherwise indistinguishable.
Why This Matters
Without breadcrumbs, a future calibrator who hits an unstated assumption has only two options: reverse-engineer the original reasoning from scratch (slow, and often impossible if the original discussion isn't preserved anywhere), or guess — and a guess risks silently overwriting something that was actually a deliberate, considered choice. Breadcrumbs turn that failure mode into a solvable task instead of a mystery.
This is the same principle behind Partial Update as Camouflage applied in reverse: just as an update should make clear what actually changed, a page in progress should make clear what hasn't been decided yet, so nobody mistakes silence for resolution.
Types of Breadcrumbs
Not all breadcrumbs resolve the same way:
- Permanent breadcrumbs — standing notes with no expected resolution date (e.g. the Master Standard's ongoing subordination to reality). These persist by design.
- Temporary breadcrumbs — open items expected to resolve eventually, but without a precisely stated trigger yet (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience").
- Trigger breadcrumbs — open items with an explicit, stated condition that retires them automatically once met (e.g. "open until three independent calibration reports exist"). Once the condition is satisfied, the breadcrumb should be removed or marked resolved — leaving it in place past its trigger is itself a form of drift.
When to Use a Breadcrumb
Leave a breadcrumb when:
- A decision was deliberately deferred, not forgotten (e.g. "Personal Standards as a Type — deliberately left undecided pending more practical experience").
- A rule or number is provisional and expected to be revisited under specific conditions (e.g. a threshold that should change once real cases test it).
- Two or more contributors genuinely disagreed and the disagreement was resolved by decision rather than consensus, and the dissenting position is worth preserving (see Standards Taxonomy: Calibration Decision Records).
- A section is a placeholder skeleton, not a finished model, and treating it as finished would be misleading.
- A commitment is being made for the future ("this will eventually need X") that could otherwise be forgotten if not tracked somewhere durable.
When Not to Use a Breadcrumb
Breadcrumbs lose their value if overused. Do not leave a breadcrumb for:
- Something that's simply finished and correct — a completed section doesn't need a note saying "this is done."
- Vague unease without a specific, nameable gap. "This might need work later" is not a breadcrumb; it's noise. A real breadcrumb names the specific open question, not just a feeling that something's unfinished.
- Something better handled by the standard field-level mechanisms already in place (e.g. `calibration_rationale`, `review_confidence`, `drift_report_status` in Admin Page Status) — don't duplicate what those fields already capture in prose form elsewhere on the page.
- An issue that's actually just a mistake needing a fix, not an open question needing a decision. A typo isn't a breadcrumb. A genuinely unresolved judgment call is.
Rule of thumb: if you can't state, in one sentence, exactly what would need to happen for the item to be considered resolved, it's not a breadcrumb yet — it's still just a worry. Sharpen it into a specific, checkable condition first.
How to Write a Good Breadcrumb
A good breadcrumb has three parts, though not always in this exact order:
- What is unresolved — stated plainly, not buried in a paragraph.
- Why it's unresolved — deliberate deferral, active disagreement, or genuinely awaiting more data. This matters because each of these three needs different handling by whoever finds it.
- What would resolve it — a specific trigger condition, not just "later" or "eventually." (E.g., "once at least one real Calibration Burden judgment has been made and checked against outcome" — not just "once we know more.")
Weak breadcrumb (avoid): "This section might need more work."
Strong breadcrumb (use this shape): "Calibration Burden is currently qualitative, not quantified. This is deliberate, not an oversight — a formula was proposed but rejected as premature. It should be revisited once at least one real Calibration Burden judgment has been made and checked against outcome."
Self-Enforcing Breadcrumbs
The strongest breadcrumbs make their own neglect visible. A basic breadcrumb just states an open item. A self-enforcing breadcrumb states what it would mean if the breadcrumb itself quietly disappeared without being resolved — turning silent removal into a flaggable Reality Override pattern rather than a clean, invisible edit.
Example (from Reality Override Game's Future Development section): "If this section is ever deleted without a worked example having been published, that is itself a Reality Override pattern worth flagging."
Not every breadcrumb needs this — it's appropriate for commitments significant enough that quietly dropping them would represent a real failure, not just tidying up.
Relationship to Other Mechanisms
Unlike Calibration Reports or Decision Records, breadcrumbs are forward-looking rather than historical. They identify unfinished calibration work rather than documenting completed calibration work — which is why they live inside the page itself, at the point of the open question, rather than in a log or report.
Breadcrumbs are not a replacement for the project's other tracking tools — they're the connective tissue between them:
- Admin Page Status fields (`drift_report_status`, `calibration_rationale`) track a page's structured metadata state.
- Calibration Reports (Talk page) track the history of what changed and why, over time.
- Calibration Decision Records (once built) will track why cross-page governance decisions were made.
- Breadcrumbs live inside the content itself, visible to anyone reading the page without needing to check any of the above separately.
Tech Insight
Breadcrumbs are a mindset before they are a mechanism. The underlying shift is refusing rigidity as a condition for progress — the belief that a page (or a system, or a decision) must be perfected before it can be built on is what actually stalls development, not incompleteness itself. Once "unresolved" is treated as a normal, visible, findable state rather than a failure to hide, it becomes possible to build forward and continue shaping the foundation at the same time, instead of being stuck waiting for a finished state that never arrives.
This is the same insight underneath Permanent Beta and Reality Override Game, applied specifically to the moment of building rather than the moment of defending an existing model. Where Reality Override Game asks "will you update when reality disagrees," this insight asks the earlier question: "will you let yourself start before everything is certain, and trust the update mechanism to catch what you got wrong." Recognizing this mindset elsewhere — anywhere a builder is stuck waiting for permission to be imperfect — is the actual transferable value of this page, beyond its specific mechanism.
See the Game. Refuse the Game. Build Better.
Structural Connections
- Slave Owner Game
- Hidden Mastery
- Foundational Statement
- One-Way Nature of the Sovereign Games
- Slave Owner Game/Tactics
- Slave Owner Game/Effects
- Slave Owner Game/Response
- Slave Owner Game/Examples
- Slave Owner Game/Applications
- Slave Owner Game/Costs to the Player
Page Transparency & Calibration
- Calibration Log & Decision Records (via Talk Page) — This page uses Talk-only calibration tracking. Full history of reviews, version changes, calibration decisions, and any governance reasoning behind structural decisions all live on the same Talk page, per Calibration Log: When to Create One and Decision Records: Governance Memory. Not every Calibration Log entry is a Decision Record — scan the Talk page's headings for entries specifically marked as decisions; the link itself being active only confirms this page has calibration history, not that a formal decision was ever recorded.
- View Current Page History — Complete edit history.
This page is under continuous calibration in line with the Permanent Beta principle.
Public Discussion Welcome
Questions, suggestions, feedback, disagreement, and proposed improvements are welcome on the Talk page.
Light rules:
- Prefer evidence and concrete examples over slogans.
- Apply Diagnostic Inversion Test when criticizing — the same standard to this page that you would apply elsewhere.
- Distinguish observation from conclusion.
- Calibration entries and Decision Records are maintenance records; public discussion belongs in ordinary Talk threads.
- This framework remains in Permanent Beta. Better calibration is always in scope.
Calibration Dependent
Pages that list this page as a load-bearing dependency:
| Page | Priority | Instrument Grade | Last Updated | Cycle Status | Drift Status |
|---|---|---|---|---|---|
| Insights and Future Layers | Core | Experimental | 2026-07-14 | Current | Breadcrumb-Open |
| Nonconformance Reporting Procedure | Core | Experimental | 2026-07-20 | Current | Breadcrumb-Open |
| Breadcrumb Tracking | Core | Experimental | 2026-07-20 | Current | Breadcrumb-Open |
| Decision Records: Governance Memory | Core | Development | 2026-07-14 | Current | Breadcrumb-Open |
If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.
Calibration Dependencies
Pages this page relies on as load-bearing dependencies: Reality Override Game If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.
Calibration References
This page is calibrated against the following core standards and reference materials:
- The Sovereign Games Framework — Overall framework philosophy and operating principles
- Permanent Beta — Core maintenance and continuous improvement standard
- Reference Standards — Principles for traceable, confirmed standards
- Calibrating Conceptual Instruments — Methodology for evaluating and refining pages
- Civilizational Traceability Hierarchy — How standards should connect to reality across levels
- Diagnostic Inversion Test — Mandatory self-application standard
- Reality Game — Foundational reality-alignment tool
- Reality Override Game — Standing discipline against protecting an existing model rather than updating it
- Observable Behavior Rule — Standing principle that diagnostics evaluate observable actions, mechanisms, and consequences, not internal motive, belief, or intent
- One-Way Nature of the Sovereign Games — Anti-capture design principles
- The Royal Cubit Civilization (Strategy) — Long-term civilizational vision and metrology metaphor
- Conceptual Instruments — Overall direction and metrology metaphor
- Breadcrumb Philosophy — Standing discipline for making unresolved questions and provisional decisions explicit
- Calibration Dependencies: Standards and Process — Rule that visible and hidden dependency lists must match, and that dependencies describe genuine reliance
Page Construction & Maintenance References
How we construct, maintain, and utilize each page as a self-admin control panel.
- Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
- Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
- Template:New Page Seed — the seed template this page's basic structure was built from.
- Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
- Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.
Calibration Procedure
In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.
Tracking & Log Pages
- Admin:Maintenance Dashboard - This dashboard shows pages that require calibration or review.
- Nonconformance Reporting Procedure — What counts as a nonconformance and where it routes.
- Known Site Issues & Fixes — Technical/mechanism bugs.
- Calibration Failure Log — Calibration-design failures.
- Breadcrumb Tracking — Live index of open Development Breadcrumbs.
- Decision Records: Governance Memory — Why governance/structural decisions exist, plus its Index.
- Insights and Future Layers — Unexpected benefits and project-wide future ideas.
- Feature Request Log — Genuinely desired features that were attempted and confirmed not currently possible with available tools. Index-only; full write-ups and discussion live on Talk.
- Calibration Report Standard Format - Standardrized reporting formatting.
Page Reference
| Title | Breadcrumb Philosophy |
|---|---|
| URL | https://www.thesovereigngames.com/wiki/Breadcrumb_Philosophy |
| Description | Defines when, why, and how to leave explicit open-items and provisional notes inside developing pages so future calibrators can find and act on them. |
| Category | Meta & Framework |