Skip to content

Reconcile finding-taxonomy vocabulary: META.a2ml [maintenance-axes] vs NEUROSYM.a2ml [finding-taxonomy] #12

Description

@hyperpolymath

Problem

Two files define the same three-axis finding taxonomy with divergent vocabulary. The executable taxonomy added in #9 (NEUROSYM.a2ml [finding-taxonomy]) was not reconciled against the pre-existing META.a2ml [maintenance-axes]:

Axis META.a2ml [maintenance-axes] (pre-existing) NEUROSYM.a2ml [finding-taxonomy] (#9)
intent (deontic) must > intend > like must / intend / wish
maintenance corrective > adaptive > perfective corrective / adaptive / perfective / preventive
locus systems > compliance > effects systems / compliance / externalities

Divergences: like vs wish, effects vs externalities (the latter chosen explicitly while building #9), and NEUROSYM adds a 4th maintenance class preventive.

Proposed resolution (option 2 — contingent on the canonical decision)

Make NEUROSYM.a2ml [finding-taxonomy] the canonical definition — it is the richer one, is executable via policies/finding_taxonomy.ecl, and already encodes the chosen externalities — and then:

  • align META.a2ml [maintenance-axes]'s three axis lines to it (wish, externalities, add preventive);
  • have META cross-reference NEUROSYM [finding-taxonomy] as the single source of truth.

This is dependent on which definition becomes canonical. If instead META's like / effects is preferred, flip the direction: update NEUROSYM [finding-taxonomy] + policies/finding_taxonomy.ecl + policies/README.adoc to match.

Affected files

  • .machine_readable/6a2/META.a2ml[maintenance-axes]
  • .machine_readable/6a2/NEUROSYM.a2ml[finding-taxonomy]
  • policies/finding_taxonomy.ecl, policies/README.adoc (only if the NEUROSYM vocabulary is the side that changes)

Surfaced during the post-extraction stale-reference sweep (#11).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactorRestructuring that preserves observable behaviour

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions