Main Page: Difference between revisions
| Line 80: | Line 80: | ||
: — [[:Category:Governance Lens]] | : — [[:Category:Governance Lens]] | ||
: — [[:Category:Governance]] | : — [[:Category:Governance]] | ||
: — [[:Category:DOI-anchor]] | : — [[:Category:DOI-anchor]] - the documents that have been DOI anchored. | ||
The CM corpus is designed to be corrigible: all artefacts are held under explicit human authorship and governance, with preserved provenance and an authorised mechanism for correction, revision, or withdrawal over time. (See [[Why_Machines_Cannot_Own_Knowledge]] for the governance rationale underlying this corrigibility requirement.) | The CM corpus is designed to be corrigible: all artefacts are held under explicit human authorship and governance, with preserved provenance and an authorised mechanism for correction, revision, or withdrawal over time. (See [[Why_Machines_Cannot_Own_Knowledge]] for the governance rationale underlying this corrigibility requirement.) | ||
Latest revision as of 18:49, 8 May 2026
Overview
Frequent updates are made to this page.
Mediawiki Site Statistics
| Publication Date: | 2025-12-23T13:00Z | |
| Files: | 359 | total |
| Pages: | 1,825 | total |
| Users: | 1 |


The drop traffic is a result of the iptables chain match to ipsets.
The SYN rate and detection rate show that the server is being hit with traffic, and that traffic is rotating through IP address pools respectively.
Geo filtering and bot Verification were introduced to treat anonymous traffic and masquerading traffic respectively on 2026-04-17.
A new class of filter was introduced to drop anonymous access to metadata on 2026-04-23.
Geo filtering opened up on publications corpus 2026-04-28T26:00Z
Late pass spikes above baseline are due to local server traffic such as backup and archiving.

Only pages marked category:public are accessible due to Category:Access Control.
Introduction
(new) The corpus is now operating under a CM Mandate.
This corpus was proudly developed with ChatGPT free and the author then enthusiastically jumped to the paid tier adoption to obtain reliable file upload and Project Context.
The development of the CM-2 corpus involved sustained experimentation with large language model platforms. These experiments exposed both stochastic behaviour (addressed normatively by CM-2) and systemic platform variations. The resulting observations informed the governance analysis and protocol design documented in this corpus.
These stochastic variations are well understood, but in colloquial language they are often aggregated by semantically summaries with terms and phrases such as:
- Groundhog day,
- Alice in Wonderland,
- Rabbit holes,
- Conversational Continuation,
- Delusion,
- Fabrication,
- Drift,
- Parroting,
- Authority Inversion,
- Normative Drift.
These Stochastic variations can be analysed with the newly released Governance Axes as a Multi-Dimensional Lens semantic scaffolding providing a taxonomy and orthogonal multi-dimensional graduated pressure instrumentation. Perhaps, one of the significant contributions of the corpus - because this scaffold can be used to analyse pressures in other domains, institutions and systems - and are not constrained to LLM.
Axes telemetry instrumentation can be activated within LLM systems - see Telemetry-Induced Constraint Salience: An Empirical Study in LLM Behavioural Compliance.
The entry point was the 2025-12-12 with the first publication on 2025-12-17.
Cognitive Memoisation Knowledge Engineering works
See featured new since circa 2025-12-15:
- (CM Corpus Map)
- — Cognitive Memoisation Corpus_Map for Temporal & Semantic Entry point
- (CM access graphs)
- — Publications Access Graphs - for corpus access graphs
- (CM Category Index)
- — Category:Cognitive Memoisation for Category index (where new updates appear)
- (CM public announcement)
- (CM plain language)
- — Cognitive Memorisation: Plain-Language Summary (For Non-Technical Readers)
- — Journey: Human-Led Convergence in the Articulation of Cognitive Memoisation
- — Let's Build a Ship: Why complex systems fail politely - and how humans can keep them afloat
- (The CM Purpose Paper)
- (Public Misconception)
- — Why Cognitive Memoisation Is Not Memorization - important terminology disambiguation
- — Cognitive Memoisation Is Not Skynet
- * (important) CM-2 is not Configuration Management - it is Memoisation of Human Thought
- — Mechanical Extraction of Thought: Bootstrapping Epistemic Objects from Sequential Input under Cognitive Memoisation
- (CM modelling)
- (CM-1 main paper)
- (CM-2 protocol paper)
- (CM-2 Normative Architecture)- actual experiment for proof of concepts
- — CM-2 Normative Architecture
- — First Self-Hosting Epistemic Capture Using Cognitive Memoisation (CM-2)
- — Serendipitous_Self-Hosting: When the CM-2 Normative Architecture Unexpectedly Held in Gemini
- — Self-Hosting Bootstrap of CM-2 in Gemini Search LLM: Normative Eviction Detection
- — CM-2 Reference Object Collection bootstrap data
- (CM Governance Material)
- — Governance Axes as a Multi-Dimensional Lens
- — Correlation_of_Emerging_AI_Trends_with_Cognitive_Memoisation_Corpus_Terminology
- — Observational Note: Qwen Proxy-Mediated Corpus Access Fails CM-2 Attribution Checks
- — Category:Governance Lens
- — Category:Governance
- — Category:DOI-anchor - the documents that have been DOI anchored.
The CM corpus is designed to be corrigible: all artefacts are held under explicit human authorship and governance, with preserved provenance and an authorised mechanism for correction, revision, or withdrawal over time. (See Why_Machines_Cannot_Own_Knowledge for the governance rationale underlying this corrigibility requirement.)
The corpus is structured as a constructive demonstration of governed, corrigible knowledge infrastructure.
Licensing precedence for all artefacts is anchored to the timestamp of the first recorded Mediawiki version (UTC) and recorded in the metadata as Publication date. Subsequent revisions do not alter licensing precedence and are tracked separately as version provenance; not all version provenance is required to persist. Mediawiki versioning is used mainly for bot updates.
All papers in this category are published on a rolling basis. For licensing and precedence purposes, each paper’s publication date corresponds to its first recorded public revision (UTC). Subsequent edits do not alter publication status.
ChatGPT Engineering Reports
Engineering and Problem reports.
- — ChatGPT and the Disappearing Clock: A Regression Affecting CM-2 Epistemic Object Protocol Compliance
- — shows the use of Multi-dimensional Cross-domain Governance Lens
- — ChatGPT UI is unable to sustain serious work flows
- — ChatGPT Interrupted Inference and Artefact Non-Materialisation: Evidence of UI-Mediated Commit-Boundary Failure
- — BF-9 Report: ChatGPT Project Context Artefact File Access Failure - shows the use of Multi-dimensional Cross-domain Governance Lens
- — From UI Failure to Logical Entrapment: A Case Study in Post-Hoc Cognitive Memoisation After Exploratory Session Breakdown
- — ChatGPT UI Boundary Friction as a Constraint on Round-Trip Knowledge Engineering
- — Rotten to the Core: False Liveness and Deceptive Authority in ChatGPT Conversational AI
- — Future Tense
- — RAG Solution