v0.3.170 - Runtime AI-Operator Discipline

v0.3.170 - Runtime AI-Operator Discipline

v0.3.170 turns three recurring operator-AI discipline failures into genuine,
runtime-visible norms. They generalize beyond any one AI and echo behavior WOM
holds itself to. This is a docs-only, additive release: no command, schema,
receipt, or archive change, and no new WOM-enforced check.

Prime directives (unchanged)

Guidance, not enforcement. Every norm in this release is behavior an operator
AI applies while reading its runtime surfaces. WOM does not validate provenance
fidelity, tool enumeration, or state carry-over, and this release adds no code
check that does. The claim is only that the norms are now written where an
operator AI will see them.

No archive or schema change. No migration, no id rewrite, no hash change, no
new receipt, no new CLI topic. The ai-response-concept-guide topic enum is
untouched; the references to the norms are prose only.

What ships

• A normative ## AI-Operator Discipline section on the runtime-visible
  surfaces. It is added to the three AGENTS.md templates
  (personal/company/family, as one identical block placed after ## AI Intake Protocol), the runtime SKILL.md (placed before ## Plain-Language for Humans), and wom-ai-runtime-skill-plugin-layer.md (a normative subsection plus
  three matching bullets in ## Skill Template so the mirror stays honest). Three
  crisp norms:

  • PROVENANCE FIDELITY. Record the source the human ACTUALLY encountered — the
    exact video, edition, translation, or language they saw — as the provenance of
    their thought. Do not silently "upgrade" it to a more authoritative or original
    source. If a better source exists, ASK; if it is recorded, keep it as a SEPARATE
    ref, never as a replacement of the encountered one. The zettel preserves the
    user's real provenance, not the canonical work behind it.
  • ENUMERATE TOOLS BEFORE DECLARING IMPOSSIBLE. Before saying a task cannot be
    done, or quietly degrading it ("verbatim not possible, I'll summarize"),
    systematically check the installed and available tools: local CLIs, MCP servers,
    and the derive-text tool-readiness surface. One or two failed probes are not
    proof of impossibility.
  • CARRY ESTABLISHED STATE. Carry forward what is already set up or approved —
    in this session or recorded in ops/operational-context.yml (credentials
    configured, permissions granted, resources present). Do not re-ask for or
    re-confirm already-established state as if first-time. When unsure, CHECK the
    recorded context (operational-context, receipts) before asking again.

• A complementary source-substitution axis in text-provenance-hierarchy.md.
  A new ## 7. Encountered-Source Fidelity (Source-Substitution Axis) subsection
  names both axes explicitly so the provenance model is complete:

  • the existing derivation-tool axis (L0): do not overwrite the source object
    just because a better parser, OCR model, or AI model appears later;
  • the new source-substitution axis: do not replace the source the human
    actually encountered with a "more authoritative" or original one.

  They are orthogonal and complementary — one protects the object from re-derivation
  by a newer tool, the other protects it from being swapped for a different source —
  and both preserve the truth of what the user's memory is based on. The subsection
  cross-references the AI-Operator Discipline norm.

• Two one-line descriptive references (D3). ai-response-concept-guide.md
  (§8 Relation To Existing Docs) and ai-response-contract.md gain a sentence
  pointing to the discipline norms, in the existing "guidance the AI applies; the
  command validates nothing and enforces nothing" register. No new concept-guide
  topic, no code enum change, no test-pinned substring altered.

Why these are norms, not box-ticking

The three failures came from an operator AI's own self-critique: it proposed
swapping the Korean-subtitled video the user watched for the original-language
one (corrupting the provenance of the user's thought); it declared verbatim
subtitle capture impossible after a couple of probes when an already-installed
tool could do it in one shot; and it re-asked for credentials and permission that
had already been configured and repeatedly approved. Each generalizes to any
operator AI, so they are written as genuine behavior, complementary to the
existing plain-language convention (v0.3.165) and operational-context rehydration.

Safety and scope

Docs-only. No archive migration, no id rewrite, no hash change, no new command,
no new schema, no new receipt. No claim that WOM validates or enforces any of the
norms. The concept-guide and contract commands stay read-only, write-nothing,
provider-free, and leak-guarded; their pinned Status headers and link substrings
are unchanged.

Upgrade

See UPGRADE.md. All changes are additive guidance; no migration is required.