Martin Lepage, PhD
Menu

Governance Methods

Governance methods and procedural infrastructure across the corpus.

A file-grounded atlas of how this corpus defines authority, distributes interpretation, and operationalizes accountability across conceptual framing, protocol design, and implementation artifacts.

This section uses the repository corpus as evidence. It preserves source titles while introducing a normalized naming and navigation layer. External files referenced by Windows paths are tracked as pending imports rather than inferred.

Read major method entries Inspect inferred tree

Corpus rows

83

Classified in inventory

Structured from frontmatter, file paths, and repository governance artifacts.

Methods pages

8

Major entries

Full-page governance method interpretations with cross-links and source paths.

Boundary discipline

3

External gaps logged

Referenced files not currently present in this workspace are preserved as pending.

Inferred Tree

Professional naming layer derived from repository evidence.

These parent groupings are normalized for site architecture while preserving source-author titles inside cards and page bodies.

conceptual-frames

Conceptual Governance Frames

Pieces that define the argument boundary: legitimacy, interruption, provenance, and the interpretive conditions of control.

protocol-design

Protocol and Procedural Design

Entries that translate framing into repeatable protocol forms, mediation logic, and accountability pathways.

methods-infrastructure

Methods and Infrastructure

Operational artifacts where governance becomes executable: app workbenches, CI gates, review templates, and runbooks.

public-translation

Companion and Public Translation Layer

Public writing, talks, and supporting records that interpret or stress-test the method from outside the core protocol layer.

Major Entries

Card and full-page method interpretations.

Each entry keeps source provenance visible and adds a normalized governance-method framing layer suitable for migration to Pharos later.

Methods and Infrastructure

Corpus Ingestion and Governance Tree

Metadata extraction, professional normalization, and boundary discipline

Source title: In-repo corpus inventory (Phase 1)

This entry documents the ingestion protocol used for the current repository corpus: source-first metadata extraction, explicit classification logic, and a dual-layer naming system that preserves original titles while introducing a professional architecture layer for cards, navigation, and migration.

Defines how files are classified, named, and grouped without erasing source-author titles.

corpus ingestionmetadata governancenaming normalizationmethod architecturemigration readiness

Methods and Infrastructure

Authored Governance Tree and Skill Ecosystem Maps

Crosswalking authored HTML tree maps to the implemented methods architecture

Source title: martin_lepage_governance_tree.html + skill_ecosystem_tree.html

This entry treats authored HTML tree maps as governance evidence, not decorative prototypes. The files `martin_lepage_governance_tree.html` and `skill_ecosystem_tree.html` encode explicit top-level families, role labels, and relationship assumptions for research, methods, infrastructure, and the SKILL ecosystem. By ingesting them directly, the site architecture can be reconciled against authored intent rather than inferred from filenames alone. The contribution is a crosswalk layer: preserving source labels exactly, introducing normalized navigation labels only where needed for consistency, and documenting where ambiguity remains. This prevents taxonomy drift, clarifies authority over section structure, and improves portability to future suites because the tree itself becomes a reviewable governance artifact.

Converts authored tree-map HTML files into explicit governance taxonomy evidence and aligns them with the site's normalized methods architecture.

taxonomy governanceauthored tree mapskill ecosystemarchitecture crosswalkprovenanceportability

Methods and Infrastructure

HEPHAISTOS Skill Operating System

Dual-engine skill architecture: execution logic plus information/tool routing

Source title: prompt engineering vs context engineering + SKILL_*.md corpus

This entry classifies the skill corpus as an operating system layer rather than a loose prompt collection. The source architecture note (`prompt engineering vs context engin.txt`) defines two coordinated engines: a Brain layer (role, execution logic, constraints, output shape) and a Map layer (knowledge retrieval, tool orchestration, memory, pruning, progressive disclosure). The SKILL files instantiate this pattern across analysis, transformation, and orchestration functions. Interpreted together, they form HEPHAISTOS: a governance runtime for bounded reasoning and output control. The key methodological contribution is architectural separation of instruction from information context so authority, traceability, and failure modes can be audited.

Formalizes the skill corpus as a small operating system with dual engines: prompt-execution logic and context/tool-map governance.

HEPHAISTOSskill operating systemconstrained cognitive architectureprompt engineeringcontext engineeringtool-first routing

Conceptual Governance Frames

Recursive Governance Under Constraint

Interruption, provenance, and control as a governance design problem

Source title: From AI Anxiety to Recursive Governance Under Constraint

This entry reads the manuscript project as a governance method: it shifts attention from affective narratives of AI anxiety to structural questions of who can interrupt systems, which traces persist after intervention, and how accountability can survive under operational constraint.

Reframes AI anxiety as an institutional control problem about interruption rights and provenance survival.

recursive governanceinterruption rightsprovenanceaccountabilityAI governance

Protocol and Procedural Design

The Sealed Card Protocol and Accountability Seams

Mediated legitimacy and proof-regime mismatch

Source title: The Sealed Card Protocol

This entry interprets The Sealed Card Protocol as a governance design for mediation seams: moments when evaluators stop trusting the object alone and begin evaluating the pathway, chain of custody, and authorization context that produced it.

Shows how legitimacy shifts from artifact content to mediation pathways when proof regimes collide.

protocol designlegitimacymediationaccountability seamstraceability

Protocol and Procedural Design

Soft Post-Control, Post-Experiment Implementation

Versioned manuscript controls after experiment-phase drafting

Source title: Pourquoi rêver encore? version packet

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.

Classifies three manuscript variants as a soft post-control layer that stabilizes interpretation after the experiment phase without claiming hard protocol enforcement.

soft post-controlpost-experiment implementationversion governancemanuscript packetinterpretive burdeneditorial control

Methods and Infrastructure

Scriptorium as Deterministic Recursive Infrastructure

From paper builder to operational governance constitution

Source title: Scriptorium

This entry interprets Scriptorium not as a writing convenience tool but as a governance infrastructure: a deterministic recursive environment that constrains interpretive drift, structures evidence hierarchy, and produces artifacts suitable for external review under institutional pressure.

Operationalizes recursive analysis into bounded, reviewable packets with explicit evidence hierarchy and disclosure layers.

Scriptoriumdeterministic methodevidence hierarchydisclosure scaffoldinggovernance infrastructure

Methods and Infrastructure

Repository Verification and Merge Controls

How CI, smoke checks, ownership mapping, and manual settings interact

Source title: verify.yml, smoke.mjs, CODEOWNERS, PR template, and README governance notes

This entry treats repository automation as governance infrastructure. It maps what is enforced in-repo (Verify workflow, smoke/build checks, ownership declarations, PR accountability prompts) and what remains external (branch protection and Cloudflare deployment controls), making the merge-control boundary explicit.

Explains the enforcement stack that gates public changes and where governance still depends on external platform settings.

CI governancesmoke testingbranch protectionCODEOWNERSdeployment control

Secondary and Supporting Entries

Lighter records for boundary tracking and unresolved evidence.

These entries are represented proportionally instead of being inflated into synthetic long-form pages.

Companion and Public Translation Layer

External Corpus Gap Register

Explicit boundary notes for not-yet-ingested files

Source title: Pending external files and absent method artifacts

This entry is a bounded register of evidentiary gaps that remain unresolved after ingesting external Windows-path sources into a documented inventory pass. It separates (1) externally ingested but not yet fully integrated clusters from (2) still-unavailable artifacts.

Records referenced files that remain unresolved after the latest external-ingestion pass.

evidence boundarypending corpusingestion gapprovenance discipline

Infrastructure Evidence

Implementation-level governance artifacts in this repo.

These files operationalize merge control, route verification, and maintainer accountability as part of the governance method itself.

Implementation artifact

Verify CI workflow

.github/workflows/verify.yml

Check gate on pull requests and pushes to main.

Implementation artifact

Smoke route harness

scripts/smoke.mjs

Build-and-preview route verification over key public surfaces.

Implementation artifact

Ownership map

.github/CODEOWNERS

Default ownership declaration for review accountability.

Implementation artifact

PR accountability template

.github/pull_request_template.md

Contributor verification and governance-change declarations.

Implementation artifact

Maintainer governance runbook

README.md

Manual GitHub and Cloudflare controls documented outside code execution.

Pending External Sources

Evidence deliberately kept unresolved until files are available.

These file references are preserved as pending so the architecture remains truthful and portable.

Pending source

To Codex for Website cards.zip

Local archive: To Codex for Website cards.zip

Referenced by user; canonical imported copy is not yet linked in-repo.

Pending source

For Her Alone to Wield The Infras.txt

Local document: For Her Alone to Wield The Infras.txt

Path referenced by user; authoritative source file still pending explicit integration.

Pending source

HEPHAISTOS AGENT artifacts

Expected as dedicated source packet if methodologically central

Skill-stack operating-system layer is now documented; standalone canonical runtime manifest is still pending.

Full Inventory

Collection-level corpus inventory with source-title preservation.

Source titles remain intact; normalized naming is used only where architecture or legibility requires it.

Projects (42)
Papers (24)

Published: 16 · In development/verification: 8

Writings (6)

  • src/content/writings/jester-femininity-and-bounded-power.md

    Jester Femininity and the Problem of Bounded Power

    A concise critical note on female power that is spectacular and central yet still structurally prevented from transforming the order that authorizes it.

  • src/content/writings/what-governance-needs-from-ritual.md

    What Governance Needs from Ritual Theory

    A short bridge essay arguing that governance often fails when it ignores ceremony, recognition, and symbolic thresholds in institutional life.

  • src/content/writings/notes-from-hexadecimal-project.md

    Notes from Hex A. Decimal

    A short essay on the writing atmosphere behind the Hex A. Decimal Substack profile: glitch-born essays, haunted systems, and a refusal of empty optimization.

  • src/content/writings/against-frictionless-governance.md

    Against Frictionless Governance

    A short essay on why governance that feels too seamless often hides the very decisions institutions most need to see, document, and defend.

  • src/content/writings/witchcraft-after-platformization.md

    Witchcraft After Platformization

    An essay on digital enchantment, visibility, affect, and the transformation of witchcraft through platforms and online circulation.

  • src/content/writings/agatha-all-along-critical-reading.md

    Agatha All Along and the Digital Reformatting of Witchcraft

    Draft essay on Agatha All Along, queer theory, ritual studies, and the digital reformatting of witchcraft.

Talks (6)