Martin Lepage, PhD
Menu
← Back to governance methods

Protocol and Procedural Design

Soft Post-Control, Post-Experiment Implementation

This entry classifies three external DOCX files for the same Rivard paper as a post-experiment soft-control packet rather than unrelated drafts. The packet preserves the same core argument while adjusting framing intensity, rhetorical pacing, and citation-weighted positioning. In governance terms, this is a control surface: edits are used to tune interpretive burden and public-readability risk after initial experimentation. The method keeps original authorial naming visible, records exact source paths, and avoids pretending these files are hard enforcement artifacts. It treats them as implementation-level editorial controls that shape how claims travel, how readers interpret scope, and how boundary statements remain legible across versions.

Protocol and Procedural Design · Phase 6 · Post-experiment soft control · Post-experiment implementation control · Implemented as external packet classification · 2026

  • soft post-control
  • post-experiment implementation
  • version governance
  • manuscript packet
  • interpretive burden
  • editorial control

Source title preserved

Pourquoi rêver encore? version packet

Source-author title is preserved in all three documents. This normalized title classifies the packet by governance function.

What this piece does

This piece formalizes the packet you identified: these three files are the soft post-control, post-experiment implementation layer for one paper, not a miscellaneous draft pile.

Packet classification and evidence

The three files share the same source title and section spine while differing in editorial control intensity.

  1. Pourquoi_rever_encore_revise.docx (about 4,116 words extracted)
  2. Pourquoi rêver [email protected] (about 5,151 words extracted)
  3. LEPAGE-Pourquoi rêver encore.docx (about 5,324 words extracted)

Across the packet, the same argument architecture stays stable:

  • title + bilingual abstract structure,
  • an introduction framed as “Cartographie de l’ame, geopolitique du reve”,
  • a shared conclusion line on “litterature de la traversee”,
  • recurring symbolic operators (double, ombre, seuil, voix feminine, silence).

What changes is not the core claim but the control profile: density, emphasis, and how explicitly social stakes are foregrounded.

Core argument

This is a governance artifact because it controls interpretation after exploration.

The packet does not enforce behavior with hard gates (like CI or merge blocks). Instead, it exerts soft control through revision pressure:

  • narrowing or widening framing,
  • shifting rhetorical certainty,
  • moving from exploratory language toward more publication-ready declarations,
  • redistributing interpretive burden between writer and reader.

That makes it a legitimate implementation layer in the method stack, especially for public-facing scholarship where language tone affects downstream interpretation and accountability.

Governance method and methodological contribution

The methodological contribution is a dual-layer model:

  1. Source-author layer: preserve original naming and argument spine across versions.
  2. Professional governance layer: classify each version by control function rather than pretending every file is a new standalone work.

This keeps provenance intact while making the packet usable for site architecture and later migration.

Power dynamics examined

Soft control concentrates power in editorial mediation.

Even without hard enforcement, revision decisions decide:

  • which claims read as cautious vs settled,
  • whether social/political stakes are foregrounded or backgrounded,
  • how much ambiguity remains open.

The packet therefore records not just content, but authority over interpretation.

Ethical stakes

If version packets are left unclassified, readers can mistake control edits for conceptual breakthroughs, or treat variant phrasing as contradiction.

Explicitly labeling this as post-experiment soft control prevents that confusion. It tells readers what changed, why it changed, and what did not change.

Recursive and systemic implications

This packet shows that governance is not only in executable scripts. It is also in editorial sequence design.

  • Hard controls protect merge and deploy pathways.
  • Soft controls stabilize argument pathways.

Both are needed for publication integrity.

Relation to other entries in the corpus

Why it matters

Naming this packet correctly closes a real governance gap.

Without this entry, the site has hard-control documentation but no explicit model for post-experiment editorial control. With it, the methods atlas now distinguishes both control families and keeps the claim boundary honest: this layer is soft, real, and consequential, but not a substitute for hard technical gates.