Martin Lepage, PhD
Menu
← Back to governance methods

Methods and Infrastructure

Authored Governance Tree and Skill Ecosystem Maps

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.

Methods and Infrastructure · Phase 1.5 · Taxonomy reconciliation · Taxonomy governance artifact · Ingested from external authored artifacts · 2026

  • taxonomy governance
  • authored tree map
  • skill ecosystem
  • architecture crosswalk
  • provenance
  • portability

Source title preserved

martin_lepage_governance_tree.html + skill_ecosystem_tree.html

Original authored map labels are preserved in source paths and interpreted as explicit taxonomy artifacts.

What this piece does

This piece establishes that authored tree maps are part of the governance layer. It ingests the external HTML map files and translates them into a reviewable taxonomy crosswalk for this site.

Core argument

A taxonomy map is a control artifact.

When the corpus author publishes a tree in executable HTML, that tree is not mere presentation. It encodes:

  • which domains are first-class,
  • what counts as parent vs child,
  • what is promoted to card-level visibility,
  • how methods, infrastructure, and companion materials are separated.

Treating those files as optional inspiration would hand architecture authority to the implementer by default. This entry argues for the opposite: authored maps must be ingested as evidence, then reconciled with the running site structure in explicit, auditable steps.

Governance method and methodological contribution

The method introduced here is authored-map reconciliation.

  1. Parse authored map artifacts as source evidence.
  2. Preserve source labels and route references in metadata.
  3. Build a normalized naming layer only for legibility and routing consistency.
  4. Record any divergence from source maps as explicit deltas.

In this pass, the authored map confirms a three-family public frame:

  • Research
  • Method
  • Governance Infrastructure

The skill map confirms the SKILL subsystem as governance infrastructure, not secondary utility content, and separates capability lanes (research, writing, strategy, orchestration, architecture).

Power dynamics examined

Tree ownership is authority ownership.

If map interpretation remains implicit, whoever edits routes can quietly redefine conceptual center and relegation boundaries. That is a governance risk: structural decisions look technical while functioning as editorial power.

This entry reduces that risk by binding tree decisions to source artifacts and publishing the crosswalk logic. It does not remove editorial power, but it makes exercise of that power visible.

Ethical stakes

The ethical issue is representational accuracy.

If the site claims to represent a methods corpus but omits authored tree evidence, readers may see an implementation-centered taxonomy that was never intended by the source author. That is a subtle form of misrepresentation.

By anchoring section structure to authored map files, the architecture can remain professional and scalable without erasing authorial conceptual force.

Recursive and systemic implications

This reconciliation pattern scales.

  • New map revisions can be ingested as deltas.
  • Existing entries can be reclassified without deleting provenance.
  • Migration to future suites can carry both source map and normalized map in parallel.

Systemically, this turns site architecture from static layout into governed metadata with explicit source-control lineage.

Current publication state

As of 2026-03-30, these authored artifacts are no longer just source files or offline exports. They are published control surfaces on the Martin site:

  • https://martin-lepage-phd.pharos-ai.ca/martin_lepage_governance_tree
  • https://martin-lepage-phd.pharos-ai.ca/skill_ecosystem_tree

Legacy PHAROS-side paths now redirect to those Martin-side URLs. That matters because the tree artifacts are part of Martin’s public methods and identity layer, while PHAROS now remains bounded to product and service surfaces only.

Relation to other entries in the corpus

Why it matters

Without authored-map reconciliation, taxonomy drift accumulates invisibly and portability claims become weak. With it, the site carries both interpretive discipline and architectural flexibility: source labels remain intact, normalized labels remain legible, public URLs point to the correct owning surface, and future migrations can reconstruct why each structural decision was made.