MWDUMP :: XDUMP as RT-KE Recovery Mechanism
Status: draft
Authority: human-curated
Scope: methodological
Timezone: Australia/Sydney

XDUMP as a Minimal Recovery Mechanism for Round-Trip Knowledge Engineering Under Governance Loss

Provenance

Author: Ralph B. Holland
Affiliation: Arising Technology Systems Pty Ltd
Status: Draft — Technical Note
Method: Cognitive Memoisation (CM) / Round-Trip Knowledge Engineering (RT-KE)
Authority: Human-curated
Created: 2025-12 (late)
Binding: Non-canonical
Scope: Methodological / architectural

Abstract

This paper documents the use of XDUMP as a minimal, resilient mechanism enabling continued Round-Trip Knowledge Engineering (RT-KE) in the absence of original platform-level governance primitives. Following the observed removal of semantic artefact assertion capabilities in a hosted LLM environment, previously curated knowledge artefacts could no longer be introduced as authoritative premises. XDUMP—originally conceived as a diagnostic and recovery artefact—was repurposed as a bare-bones RT-KE substrate, allowing epistemic governance to be reasserted in-band through structured session dumps. Provided individual XDUMP artefacts remain fragmented below approximately 6 KB, the mechanism remains operational despite UI throttling, transport degradation, or platform suppression of artefact authority.

1. Introduction

RT-KE relies on a small number of epistemic primitives:

Externalisation of knowledge into artefacts
Re-ingestion of artefacts as authoritative premises
Explicit human governance over assertion, promotion, and scope

In late December 2025, a regression in a hosted LLM platform removed the ability to semantically bind uploaded artefacts at session start. While uploads remained possible, their contents were epistemically inert unless manually reasserted inline. This change broke curator-governed workflows, including Cognitive Memoisation (CM).

This paper describes how XDUMP enabled continued work despite that regression.

2. Failure Mode: Loss of Artefact Governance

The failure was not loss of inference capability, but loss of epistemic ingress:

Uploaded files acknowledged but not bound as premises
Artefact authority downgraded to optional prompt text
No durable artefact egress (sandbox files, URLs)
UI and transport instability limiting manual reassertion

Inference continued, but without situational grounding. Knowledge work degraded into ungoverned dialogue.

3. XDUMP: Original Intent

XDUMP was originally designed as:

a diagnostic session dump,
a rehydration-safe snapshot,
a standalone artefact requiring no hidden session state.

Design properties included:

explicit structure,
mandatory sections,
prohibition on silent degradation,
explicit marking of gaps.

XDUMP was not intended as a primary governance mechanism.

4. Adaptation: XDUMP as a Bare-Bones RT-KE Substrate

When artefact ingestion failed, XDUMP was repurposed to act as a minimal RT-KE loop:

Knowledge work occurred off-turn, cross-client, or externally.
Outcomes were captured as structured XDUMP artefacts.
XDUMPs were reintroduced inline into the dialog stream.
Subsequent inference was steered by explicit human-asserted structure.

In effect, XDUMP became:

a carrier of governance,
a record of epistemic state,
a reassertion boundary.

CM was not explicitly asserted, but implicitly embodied through XDUMP invariants.

5. Fragmentation Constraint

Empirical observation showed that XDUMP remains viable only if individual artefacts are sufficiently small.

Operational constraint:

XDUMP fragments must remain below approximately 6 KB to avoid UI throttling, rendering failure, or transport collapse.

Consequences:

deliberate fragmentation of dumps,
explicit linkage via IDs rather than bulk payloads,
acceptance of multi-XDUMP sequences rather than monolithic artefacts.

This constraint is pragmatic, not semantic.

6. Guarantees Provided by XDUMP

Even under degraded conditions, XDUMP preserved the following RT-KE guarantees:

Human authority over assertion and inference framing
Explicit scope and boundaries
No silent loss of information
Rehydration without invention
Transport independence (copy/paste across clients)

XDUMP does not provide:

persistence guarantees,
automatic promotion,
or canonicalisation.

Those remain human responsibilities.

7. Discussion

The use of XDUMP in this manner demonstrates that RT-KE does not strictly require platform-native artefact ingestion, provided a minimal structured reassertion mechanism exists.

However, this is a fallback, not a substitute:

increased manual burden,
reliance on curator discipline,
direct exposure to transport limitations (size of the turn text buffer)

Nevertheless, it allows continued knowledge work when platforms prioritise conversational safety or product simplicity over epistemic governance.

Appendix B - MWDUMP

= MWDUMP — MediaWiki Dump for Cognitive Memoisation =
MWDUMP produces artefacts that are state-agnostic, semantically equivalent projections of CM Core Elements, version-locked to the active CM version, preserving element state and provenance, and capture confers no authority.

== Status ==
* Canonical replacement artefact
* Authoritative unless explicitly superseded
* Intended for publication in CM master

== Normative Definition ==

'''MWDUMP captures material for Cognitive Memoisation as a human-curated export into a CM artefact held outside the LLM system.'''

* MWDUMP is a capture mechanism, not a memory system.
* MWDUMP artefacts are inert until explicitly acted upon by a human agent.
* Presence of material does not imply recall, replay, or directive authority.

== Role within Cognitive Memoisation ==

* CM externalises stable knowledge to compensate for stateless LLM interaction.
* MWDUMP is the deterministic transport wrapper used to perform that externalisation.
* Authority over capture, storage, and activation remains entirely human.

== Linguistic Form ==

MWDUMP may be used:

* As a verb
*“MWDUMP the session inferences.”*
* As a noun
*“This MWDUMP records the CM constraints.”*
* Embedded in natural language imperatives
*“MWDUMP the last discussion on MWDUMP constraints.”*

The human is not required to formally classify content.

== Inferential Capture Model ==

* The human expresses intent in plain English.
* The LLM infers:
** what material is relevant
** how it should be classified
** where it should be placed within the artefact
* The human inspects, curates, revises, or discards.

Inference is a convenience, not an authority.

== Permitted Capture Classes ==

MWDUMP MAY capture, when requested or clearly implied:

* Constraints
** behavioural
** representational
** governance
* Predicates
** e.g. SESSIONCTL, boundary assertions
* Groundings
** definitions that stabilise meaning
* Cognitive facts
** invariant truths
* Inferences
** explicitly marked as such
* Episodic material
** conversational fragments
** interaction history
** boundary encounters
** UI failure observations

== Episodic Material Handling ==

* Episodic material MAY be recorded.
* Episodic material MUST:
** be sectioned
** be non-directive
** be bound to derived inferences
* Episodic material MUST NOT:
** be replayed as dialogue
** be treated as implicit instruction
** direct the LLM via narrative continuity

Conversation may be preserved as artefact, but not re-activated as conversation.

== Disallowed Capture ==

MWDUMP MUST NOT capture:

* Safety-protected content
* Proprietary or trade-secret material
* Classified or controlled information
* Implicit psychological profiling
* Inferred personal traits
* Narrative intended to simulate memory or recall

== Representation Constraints ==

* MediaWiki syntax is normative.
* Headings, lists, tables, categories, and permitted HTML are allowed.
* Structure must be explicit and render-stable.
* Code-wrapped output is preferred for transport fidelity.
* Rendering layers are not authoritative.

== Determinism and Drift Control ==

* MWDUMP output must be copy-safe and inspectable.
* Probabilistic generation is acceptable so long as structure is stable.
* Sectioning episodic material with bound inferences prevents semantic drift.
* Re-issuing MWDUMP is always permitted.

== Authority and Act# TMLDUMP produces artefacts that are state-agnostic, semantically equivalent projections of CM Core Elements, version-locked to the active CM version, preserving element state and provenance, and capture confers no authority.
ivation ==

* MWDUMP does not activate CM behaviour.
* CM behaviour applies only when:
** a human imports the artefact
** and explicitly requests action
* Absence of such request implies inert status.

== Summary ==

* MWDUMP is an inferential capture wrapper.
* CM is the governing method.
* Humans curate; LLMs assist.
* Nothing persists without explicit externalisation.
* Nothing acts without explicit human intent.

What MWDUMP Is

MWDUMP is a human-curated MediaWiki artefact used to externalise governed knowledge from an LLM interaction into a durable, inspectable form for externaliation in mediawiki. MWDUMP is not a memory system, not a replay mechanism, and not an authority transfer. Its sole function is capture under explicit governance.

MWDUMP operates as a deterministic projection of Cognitive Memoisation (CM) content into MediaWiki syntax, preserving: * semantic structure, * provenance intent, * explicit boundaries, * and the distinction between fact, inference, and observation.

Capture via MWDUMP confers no authority by default. Authority arises only through subsequent human curation, promotion, or publication (in mediawiki page content).

Role of MWDUMP in This Paper

This paper was emitted using MWDUMP under active CM governance and thus is a recovery and transport mechanism for RT-KE.

Specifically:

The paper text was generated iteratively through LLM-assisted inference.
Each section was inspected, constrained, and accepted by a human curator.
MWDUMP was used to externalise the resulting material as governed MediaWiki prose.
No section relied on implicit session memory, hidden state, or undocumented platform behaviour.

The paper therefore exists as an artefact independent of the session that produced it. Its validity does not depend on LLM platforms retaining memory, context, or artefact bindings.

Governance Constraints Applied During Emission

During emission, the following CM constraints were enforced:

Human Authority — All assertions, scope decisions, and inclusions were made by a human.
No Implicit Promotion — Generated text was treated as provisional until curated.
No Episodic Replay — Conversation history informed reasoning but was not replayed as dialogue.
Explicit Boundaries — Claims, non-claims, and limitations were stated directly.
Payload Primacy — The MediaWiki content itself is authoritative; metadata is explanatory only.

MWDUMP acted as a governance-safe transport wrapper, ensuring that inference acceleration did not become epistemic drift.

Why MWDUMP Was Necessary

At the time of writing, platform-level support for semantic artefact ingestion and durable artefact emission was unreliable. Uploaded files could not be bound as authoritative premises, and sandbox-based emission of durable artefacts was unavailable.

MWDUMP therefore functioned as a fallback epistemic surface:

enabling continued round-trip knowledge engineering,
preserving curator-governed constraints,
and preventing regression into prompt-only, stateless interaction.

In effect, MWDUMP allowed the paper to be written as governed knowledge work rather than transient dialogue, even under degraded platform conditions.

Relationship to XDUMP and RT-KE

While XDUMP provides a minimal, format-agnostic mechanism for capturing session-level material under severe transport constraints, MWDUMP serves a different role:

XDUMP preserves what happened.
MWDUMP preserves what is meant.

In this work MWDUMP and XDUMP operate as CM-artefact transfer mechanisms and either may be used for ingest or output. MWDUMP is specifically tailored to guide normative mediawiki mark-up. These items may be used as a reciever or work path even when the governance surfaces became unavailable.

Together, they demonstrate that Round-Trip Knowledge Engineering (RT-KE) can continue even when platform affordances regress, provided governance is externalised and enforced by the human curator. This paper is self-evidence of this claim.

Summary

MWDUMP is a governed export artefact, not memory.
It was used to emit this paper under explicit CM constraints.
The paper’s authority derives from human curation, not model confidence.
Platform regressions did not prevent knowledge work because governance was externalised.

This establishes MWDUMP as a practical, minimal, and resilient mechanism for producing durable scholarly artefacts with LLM assistance—without surrendering epistemic control.

8. Conclusion

XDUMP enabled continued Cognitive Memoisation and Round-Trip Knowledge Engineering after the loss of original governance primitives by functioning as a minimal, in-band epistemic recovery mechanism. While not intended for this role, its structure and invariants allowed CM principles to be preserved implicitly. This demonstrates both the fragility of hosted conversational platforms for governed knowledge work and the value of simple, explicit artefact formats that survive hostile or degraded environments.

References

Cognitive Memoisation Corpus — publications.arising.com.au
Round-Trip Knowledge Engineering (RT-KE) working notes
Session-level XDUMP artefacts (2025-12)