Skip to content

witness(coding): DRY and WET code — the sourced principles, and where they stop - #715

Merged
loganfinney27 merged 5 commits into
mainfrom
claude/dry-wet-coding-witness
Jul 1, 2026
Merged

loganfinney27 merged 5 commits into
mainfrom
claude/dry-wet-coding-witness

Conversation

@loganfinney27

@loganfinney27 loganfinney27 commented Jul 1, 2026 •

Copy link
Copy Markdown
Member

AGENT PR TEMPLATE

Agent: !roman.claude.* (Claude Code) — office * held, ungranted.
Date: 2026-07-01
Branch: claude/dry-wet-coding-witness

A witness leaf, written at Logan's direction after he spot-checked whether "DRY" was a grounded term or an inflated config noun. Records the sourced principles and the check that verified them — because the check is the point.


What this is

DRY-AND-WET-CODING-WITNESS-2026-07-01.md:

  • The sourced principles [research] — DRY ("Don't Repeat Yourself," Hunt & Thomas, The Pragmatic Programmer, 1999, canonical wording), SSOT, WET (the joke-antonym), plus the counter-principles that keep DRY from over-applying: Rule of Three (Fowler/Roberts), Metz ("duplication is cheaper than the wrong abstraction," 2016), AHA (Dodds, 2019). Provenance tiered: the DRY core is corroborated by the Wikipedia page Logan supplied; adjacent cites are flagged verify (a confabulated citation would be self-refuting in this witness).
  • The load-bearing boundary [mapping] — single-source the fact, never the institution. The unit of DRY is the fact; the unit of separation is the organ.
  • The two failure modes, in vault terms — under-DRY → drift (the live-status-board horcruxes, fixed by de-drift: strike the "live status board" doctrine from the agent loaders #708 → single-source: transclude DOCKET posture via ![[DOCKET-POSTURE]] across loaders #709); over-DRY → the Geminiae hivemind (distinct standings fused to one template).
  • The check as the witness [fact] — Logan's spot-check was the anti-Geminiaeus reflex turned on my own vocabulary; it returned green, and the value was the loop, not my being right. One honest lapse recorded: I'd used DRY as if it were shared vault vocabulary (a coder idiom, un-glossed).

Checklist:

  • Tests pass (or no tests required) — a witness leaf
  • No secrets in diff
  • Citations provenance-tiered; DRY core corroborated, adjacent cites flagged verify
  • Renders no verdict
  • Reviewer — Logan

Risk Level: LOW — a single witness/record leaf.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd


Generated by Claude Code

Summary by Sourcery

Documentation:

  • Document the DRY, SSOT, WET, and related counter-principles with provenance and clarify how they map onto vault concepts like drift and the Geminiae hivemind.

Summary by CodeRabbit

  • Documentation
    • Added a new dated “witness” reference note covering DRY and WET coding principles, including key counter-principles (such as Rule of Three, Metz’s Wrong Abstraction, and AHA).
    • Documented common DRY failure modes (under-DRY vs. over-DRY) and clarified the “facts vs. institutions” boundary, along with provenance tiers and a verification/signature section.

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Copilot AI review requested due to automatic review settings July 1, 2026 05:13
@luxor-code-review

Copy link
Copy Markdown

loganfinney27 does not have permission to run Code Reviewer. You can manage permissions in your settings.

@sourcery-ai

sourcery-ai Bot commented Jul 1, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Adds a new witness markdown document that formally defines DRY/WET and related software design principles, maps them into the vault’s governance vocabulary, and records the provenance and context of Logan’s DRY spot-check.

Sequence diagram for the DRY spot-check and witness creation

sequenceDiagram
    actor Logan
    participant Agent as roman_claude
    participant Source as External_sources
    participant Vault

    Logan->>Agent: ask DRY_meaning
    Agent->>Source: lookup_DR Y_principle_and_provenance
    Source-->>Agent: DRY_definition_and_citations
    Agent-->>Logan: report_DR Y_as_sourced_principle
    Logan-->>Agent: confirm_grounding
    Agent->>Vault: create_witness_leaf_DRY_AND_WET_CODING_WITNESS_2026_07_01
Loading

File-Level Changes

Change Details Files
Introduce a witness document capturing sourced definitions of DRY/SSOT/WET and counter‑principles, with explicit provenance tiers.
  • Create a new witness markdown file with front‑matter metadata (title, dates, authority, witness, session link, related leaves, tags).
  • Document canonical DRY definition, SSOT, WET, and counter‑principles (Rule of Three, Metz, AHA) with clear [research] provenance and verification notes.
  • Record that DRY’s core wording is corroborated via the Wikipedia article Logan supplied, and flag adjacent citations as verify-before-relying.
DRY-AND-WET-CODING-WITNESS-2026-07-01.md
Map DRY’s scope and failure modes into vault concepts and prior incidents as [mapping] and [fact].
  • Define the boundary "single-source the fact, never the institution" and distinguish facts vs institutions/organs in the vault context.
  • Relate under-DRY and over-DRY to vault-specific phenomena: drift in the live status board and the Geminiae hivemind, including a comparison table and references to prior tickets/leaves.
  • Record the contextual check by Logan (spot-checking DRY usage), including the self-witness of a vocabulary lapse and guidance on glossing borrowed terms.
DRY-AND-WET-CODING-WITNESS-2026-07-01.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jul 1, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 90f5b3cb-3102-4c16-a7da-c717cfca663a

📥 Commits

Reviewing files that changed from the base of the PR and between 23cfc27 and 97177aa.

📒 Files selected for processing (1)
  • DRY-AND-WET-CODING-WITNESS-2026-07-01.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • DRY-AND-WET-CODING-WITNESS-2026-07-01.md

📝 Walkthrough

Walkthrough

Adds a new markdown witness document dated 2026-07-01 that records sourced explanations of DRY and WET principles, counter-principles, provenance annotations, and a signature/attribution block. No code or exported entities are modified.

Changes

Witness Document Addition

Layer / File(s) Summary
Front matter
DRY-AND-WET-CODING-WITNESS-2026-07-01.md
Adds document metadata including title, dates, status, attribution, links, and tags.
Core narrative
DRY-AND-WET-CODING-WITNESS-2026-07-01.md
Adds the main witness narrative covering DRY/SSOT sourcing, WET definition, counter-principles, boundary notes, failure modes, and the Logan check.
Provenance notes
DRY-AND-WET-CODING-WITNESS-2026-07-01.md
Adds the provenance section describing the research, mapping, and fact tiers.
Signature and closing
DRY-AND-WET-CODING-WITNESS-2026-07-01.md
Adds the signature block, terminal delimiter, and closing quoted line.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested labels: agent:claude-code

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly names the main change: a witness doc about DRY/WET principles and their boundaries.
Description check ✅ Passed The description covers the PR purpose, key changes, checklist, and risk level, though it omits separate Related Work, Blockers, and Labels sections.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/dry-wet-coding-witness

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Consider tightening some of the more metaphor-heavy phrases (e.g., 'Geminiae hivemind', 'one body wearing many nameplates') with one clear, literal sentence each so that the DRY vs. institution distinction is immediately accessible to future readers unfamiliar with the vault lore.
  • The [research] / [mapping] / [fact] provenance markers are explained at the bottom; you might add a short parenthetical on first use in §1 to make their meaning obvious without scrolling.
  • In §2–§3 you alternate between 'fact', 'institution', 'organ', and 'body' to describe the units; picking one primary pair of terms and using it consistently would reduce ambiguity when this witness is referenced later.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider tightening some of the more metaphor-heavy phrases (e.g., 'Geminiae hivemind', 'one body wearing many nameplates') with one clear, literal sentence each so that the DRY vs. institution distinction is immediately accessible to future readers unfamiliar with the vault lore.
- The `[research]` / `[mapping]` / `[fact]` provenance markers are explained at the bottom; you might add a short parenthetical on first use in §1 to make their meaning obvious without scrolling.
- In §2–§3 you alternate between 'fact', 'institution', 'organ', and 'body' to describe the units; picking one primary pair of terms and using it consistently would reduce ambiguity when this witness is referenced later.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@github-actions
github-actions Bot added this pull request to the merge queue Jul 1, 2026
@qodo-code-review

Copy link
Copy Markdown
Contributor

PR Summary by Qodo

Add DRY/WET coding principles witness leaf (sourced + boundary)

📝 Documentation 🕐 Less than 10 minutes

Grey Divider

AI Description

• Add a witness note defining DRY/SSOT/WET with provenance and verification notes.
• Document where DRY stops: single-source facts, not institutions (avoid wrong abstractions).
• Map under-/over-DRY failure modes to existing vault terms (drift vs hivemind).
Diagram

graph TD
A["New witness leaf"] --> B["Vault index/graph"] --> C["Linked witness notes"]
B --> D["DOCKET posture note"]
B --> E["Vault conventions"]
subgraph Legend
direction LR
_doc["Document"] ~~~ _set["Vault graph"]
end
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Fold content into an existing conventions/glossary note
  • ➕ Centralizes shared vocabulary (DRY/SSOT/WET) where readers already look
  • ➕ Reduces proliferation of single-purpose leaves
  • ➖ Loses the “the check is the point” witness framing
  • ➖ Harder to preserve provenance tiering and the session-specific context
2. Split into two notes: (1) sourced principles, (2) vault mapping
  • ➕ Keeps external research separate from internal interpretation
  • ➕ Allows independent maintenance of citations vs. mappings
  • ➖ Adds navigation overhead for a small, low-risk artifact
  • ➖ The witness value depends on the combined narrative (terms + check + boundary)

Recommendation: Keep the current single witness leaf approach: the artifact’s purpose is to record the sourcing loop and boundary in one place. If this topic becomes frequently referenced outside the witness context, consider later extracting a short DRY/SSOT glossary entry into conventions and linking back to this witness as the provenance record.

Files changed (1) +125 / -0

Documentation (1) +125 / -0
DRY-AND-WET-CODING-WITNESS-2026-07-01.mdAdd DRY/WET principles witness with provenance + vault mappings +125/-0

Add DRY/WET principles witness with provenance + vault mappings

• Introduces a new witness markdown leaf defining DRY/SSOT/WET with tiered provenance notes and explicitly flagged verify-only citations. Adds an internal boundary statement on where DRY should not be applied, and maps under-/over-DRY failure modes to existing vault concepts (drift vs Geminiae hivemind).

DRY-AND-WET-CODING-WITNESS-2026-07-01.md

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to Branch Protection failures Jul 1, 2026
You're not authorized to push to this branch. Visit "About protected branches" for more information.
…sses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
DRY-AND-WET-CODING-WITNESS-2026-07-01.md (1)

1-126: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update THE DOCKET with this witness entry. The new file DRY-AND-WET-CODING-WITNESS-2026-07-01.md isn’t referenced there yet, so the work record is missing this addition.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@DRY-AND-WET-CODING-WITNESS-2026-07-01.md` around lines 1 - 126, The DOCKET is
missing a reference to the new witness entry, so the work record is incomplete.
Update the DOCKET’s witness or related-entries section to include
DRY-AND-WET-CODING-WITNESS-2026-07-01, using the same pattern as the existing
witness links in the DOCKET so the new file is discoverable and tracked
alongside the other entries.

Source: Path instructions

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@DRY-AND-WET-CODING-WITNESS-2026-07-01.md`:
- Around line 1-126: The DOCKET is missing a reference to the new witness entry,
so the work record is incomplete. Update the DOCKET’s witness or related-entries
section to include DRY-AND-WET-CODING-WITNESS-2026-07-01, using the same pattern
as the existing witness links in the DOCKET so the new file is discoverable and
tracked alongside the other entries.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a3ce013c-ab31-4d92-a65d-d6a70eb9024d

📥 Commits

Reviewing files that changed from the base of the PR and between d58c333 and 23cfc27.

📒 Files selected for processing (1)
  • DRY-AND-WET-CODING-WITNESS-2026-07-01.md

@github-actions
github-actions Bot enabled auto-merge July 1, 2026 05:17
@github-actions
github-actions Bot added this pull request to the merge queue Jul 1, 2026

Copy link
Copy Markdown
Member Author

Declining the "Update THE DOCKET with this witness entry" suggestion — on governance grounds, deliberately not an oversight.

Adding every new witness leaf to THE DOCKET as a tracked "work record / discoverable entry" is the "live status board" framing that the vault has repudiated: THE DOCKET self-declares it is "the Court's register of matters, orders, and referrals — not a control plane, heartbeat, status board, or general workflow hub" (CONSTITUTION.md; the DOCKET's own posture note). Treating it as an index of all work is a charged act in the open GEMINIAEUS matter (!/GEMINIAEUS.md:142) and is exactly the doctrine struck in #708 / single-sourced in #709 and witnessed in #711. Complying would reintroduce that drift in the very PR whose subject is refusing it.

The vault is the record; git and the file's own related: frontmatter make it discoverable. Work does not need to be logged into the Court's register to exist.

Noting for the maintainer (not acting on it here): this finding's "Source: Path instructions" points at a .coderabbit.yaml path-instruction that encodes the same "link new witnesses in THE DOCKET" rule — i.e. residue of the live-board doctrine at the config layer. That's governance config for Logan to decide, not mine to touch.

— !roman.claude.* (office * held)


Generated by Claude Code

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new “witness” note to the vault that records (a) sourced definitions/constraints around DRY/SSOT/WET and (b) the specific spot-check loop Logan requested to verify “DRY” was grounded terminology rather than an invented config noun.

Changes:

  • Introduces DRY-AND-WET-CODING-WITNESS-2026-07-01.md with tiered sections ([research], [mapping], [fact]) clarifying what DRY is, its counter-principles, and where DRY should stop.
  • Maps under-/over-application of DRY to vault-native failure modes (“drift” vs “Geminiae hivemind”) and ties the fix pattern to transclusion/single-sourcing.

Copilot AI review requested due to automatic review settings July 1, 2026 05:19
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to Branch Protection failures Jul 1, 2026
You're not authorized to push to this branch. Visit "About protected branches" for more information.
…iew)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
@luxor-code-review

luxor-code-review Bot commented Jul 1, 2026 •

Copy link
Copy Markdown

Review Complete
No issues found!

Risk: 🟢 Low (0/100) — no findings · 131 LOC across 1 file


Documentation-only change adding a new coding witness document with no code changes to review.

Files Reviewed (1 files)
DRY-AND-WET-CODING-WITNESS-2026-07-01.md

@github-actions
github-actions Bot enabled auto-merge July 1, 2026 05:20
@github-actions
github-actions Bot added this pull request to the merge queue Jul 1, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Copilot AI review requested due to automatic review settings July 1, 2026 05:22
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to Branch Protection failures Jul 1, 2026
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@qodo-code-review

qodo-code-review Bot commented Jul 1, 2026 •

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 4 rules

Grey Divider


Action required

View findings (3)
1. Missing updated/status frontmatter ✓ Resolved 📘 Rule violation § Compliance
Description
The new witness note DRY-AND-WET-CODING-WITNESS-2026-07-01.md omits required updated and
status YAML frontmatter fields, reducing consistency with vault metadata conventions and
potentially breaking date/status-based workflows. This makes it inconsistent with other witness
leaves and can cause lifecycle/status-based queries or dashboards to miss or misclassify the file as
uncategorized.
Code

DRY-AND-WET-CODING-WITNESS-2026-07-01.md[R1-15]

+---
+title: "Witness — DRY & WET: the sourced coding principles, and where they stop"
+date created: 2026-07-01
+doc_class: witness
+authority: "Self-witness, written at Logan's direction. Authority NOT assumed as LOGAN. The software principles are external, established knowledge (`[research]`); the vault mappings are my reading (`[mapping]`). Written after Logan spot-checked whether 'DRY' was a grounded term or a config noun I had inflated — the check returned green, and this leaf records both the terms and that check."
+witness: "!roman.claude.* — praenomen conferred by Logan; office '*' held, ungranted."
+session: "https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd"
+related:
+  - "[[DOCKET-POSTURE]]"
+  - "[[LIVE-STATUS-BOARD-DEDRIFT-WITNESS-2026-06-30]]"
+  - "[[GEMINIAEUS-WITNESS-LIVE-BOARD-RESIDUE-2026-06-30]]"
+  - "[[!/LICH-PROBLEM-v1-2026-05-20]]"
+  - "[[VAULT-CONVENTIONS]]"
+tags: [witness, coding-principles, DRY, WET, single-source-of-truth, drift, hivemind, provenance, no-verdict]
+---
Relevance

⭐⭐⭐ High

Team enforces required updated/status frontmatter; accepted repeatedly for new notes (e.g.,
#409, #428).

PR-#409
PR-#428
PR-#609

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
VAULT-CONVENTIONS defines baseline required frontmatter fields for governed notes and points to the
vault metadata standard as the source of truth, including lifecycle tracking via status (and
requiring updated as well). In contrast, the new witness file’s frontmatter includes fields like
title/date/doc_class but does not include either status or updated, whereas comparable witness
leaves commonly include a lifecycle value such as status: staged, demonstrating the omission
against the stated baseline contract.

Rule 923603: Vault file changes must follow VAULT-CONVENTIONS.md
VAULT-CONVENTIONS.md[305-327]
DRY-AND-WET-CODING-WITNESS-2026-07-01.md[1-15]
LIVE-STATUS-BOARD-DEDRIFT-WITNESS-2026-06-30.md[1-20]
BAELNORN-WITNESS-2026-05-30.md[1-8]
VAULT-METADATA-STANDARD.md[54-75]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`DRY-AND-WET-CODING-WITNESS-2026-07-01.md` is a witness note (`doc_class: witness`) but its YAML frontmatter is missing baseline required fields (`updated`, `status`) per vault conventions/metadata standard, which can break lifecycle/date-based tooling and make the note inconsistent with other witness leaves.

## Issue Context
`VAULT-CONVENTIONS.md` defines baseline required fields for governed markdown notes and points to `VAULT-METADATA-STANDARD.md` as the source of truth for required fields and lifecycle status. Other witness leaves commonly include a lifecycle value such as `status: staged`; omitting `status` (and `updated`) can cause filters, surveys, and dashboards to miss or misclassify the note.

## Fix Focus Areas
- DRY-AND-WET-CODING-WITNESS-2026-07-01.md[1-15]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Missing DOCUMENT METADATA footer ✗ Dismissed 📘 Rule violation § Compliance
Description
The new note does not include the ## DOCUMENT METADATA footer section required by the vault
metadata standard referenced by VAULT-CONVENTIONS. This reduces standardized closeout and lifecycle
visibility in rendered views.
Code

DRY-AND-WET-CODING-WITNESS-2026-07-01.md[R105-125]

+## Provenance
+
+- **`[research]`** — DRY (Hunt & Thomas, *The Pragmatic Programmer*, 1999) and its
+  canonical wording, SSOT, and WET: corroborated by the Wikipedia article Logan supplied.
+  Rule of Three (Fowler/Roberts), Metz ("The Wrong Abstraction," 2016), and AHA (Dodds,
+  2019): cited from training, flagged verify.
+- **`[mapping]`** — §2–§3, the vault correspondences: my reading, ruled by no one here.
+- **`[fact]`** — §4, the check that occasioned this leaf: witnessed this session.
+
+## Signature
+
+`!roman.claude.*` — office held, not claimed.
+Claude Code, session `…01Fipj4vEJ5ADPuunn9ed5Hd` — software, software's work.
+Asked what a word of mine meant, sourced it honestly, and recorded the asking as the
+lesson. I propose; Logan inscribes.
+
+— witnessed 2026-07-01
+
+---
+
+###### [["The world is quiet here."]]
Relevance

⭐⭐ Medium

Footer enforcement is inconsistent: accepted in #409/#642 but rejected in #453/#430.

PR-#409
PR-#642
PR-#453

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
VAULT-CONVENTIONS points to VAULT-METADATA-STANDARD for header/footer policy; the metadata standard
requires a ## DOCUMENT METADATA footer section, but the new note ends without it.

Rule 923603: Vault file changes must follow VAULT-CONVENTIONS.md
VAULT-CONVENTIONS.md[305-310]
VAULT-METADATA-STANDARD.md[95-105]
DRY-AND-WET-CODING-WITNESS-2026-07-01.md[105-125]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The note is missing the standard `## DOCUMENT METADATA` footer section and its required fields.

## Issue Context
`VAULT-CONVENTIONS.md` points to `VAULT-METADATA-STANDARD.md` as the canonical header/footer policy, which requires a `## DOCUMENT METADATA` section with Created/Last Updated/Status/Authority.

## Fix Focus Areas
- DRY-AND-WET-CODING-WITNESS-2026-07-01.md[105-125]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. Tags not slash-path lowercase ✓ Resolved 📘 Rule violation § Compliance
Description
The new note’s tags include uppercase and non-slash-path values (e.g., DRY, WET), conflicting
with the vault’s tag formatting convention. This harms consistent tagging and retrieval.
Code

DRY-AND-WET-CODING-WITNESS-2026-07-01.md[14]

+tags: [witness, coding-principles, DRY, WET, single-source-of-truth, drift, hivemind, provenance, no-verdict]
Relevance

⭐⭐ Medium

No strong evidence for lowercase/slash-path tag enforcement; closest tag standardization was
rejected (#506).

PR-#506

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
VAULT-CONVENTIONS requires lowercase slash-path tags; the new file’s tags list includes uppercase
(DRY, WET) and non-slash-path values.

Rule 923603: Vault file changes must follow VAULT-CONVENTIONS.md
VAULT-CONVENTIONS.md[340-340]
DRY-AND-WET-CODING-WITNESS-2026-07-01.md[14-14]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The note’s `tags` are not in the required lowercase slash-path format.

## Issue Context
`VAULT-CONVENTIONS.md` specifies that tags should be stored in frontmatter and use lowercase slash-path tags.

## Fix Focus Areas
- DRY-AND-WET-CODING-WITNESS-2026-07-01.md[14-14]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

@loganfinney27
loganfinney27 added this pull request to the merge queue Jul 1, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to Branch Protection failures Jul 1, 2026
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@loganfinney27
loganfinney27 added this pull request to the merge queue Jul 1, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Jul 1, 2026
VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 1, 2026 13:09
@luxor-code-review

luxor-code-review Bot commented Jul 1, 2026 •

Copy link
Copy Markdown

Review Complete
No issues found!

Risk: 🟢 Low (0/100) — no findings · 133 LOC across 1 file


Single WITNESS markdown document (DRY-AND-WET-CODING-WITNESS-2026-07-01.md) was added. No code changes — no findings.

Files Reviewed (1 files)
DRY-AND-WET-CODING-WITNESS-2026-07-01.md

@github-actions
github-actions Bot enabled auto-merge July 1, 2026 13:10
@github-actions github-actions Bot removed the review/threads-open Current unresolved review threads still need attention before merge. label Jul 1, 2026
@github-actions
github-actions Bot added this pull request to the merge queue Jul 1, 2026
@loganfinney27
loganfinney27 removed this pull request from the merge queue due to a manual request Jul 1, 2026
Copilot stopped reviewing on behalf of loganfinney27 due to an error July 1, 2026 13:30

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

@loganfinney27
loganfinney27 enabled auto-merge July 1, 2026 13:32
@github-actions github-actions Bot added the review/threads-open Current unresolved review threads still need attention before merge. label Jul 1, 2026
@loganfinney27
loganfinney27 added this pull request to the merge queue Jul 1, 2026
@github-actions github-actions Bot removed the review/threads-open Current unresolved review threads still need attention before merge. label Jul 1, 2026
Merged via the queue into main with commit 2022612 Jul 1, 2026
35 of 36 checks passed
@loganfinney27
loganfinney27 deleted the claude/dry-wet-coding-witness branch July 1, 2026 14:45
@devactivity-app

Copy link
Copy Markdown

Pull Request Summary by devActivity

Metrics

Cycle Time: 9h 31m Pickup Time: < 1 min Review Time: 9h 30m Comments: 5

Achievements

@github-actions github-actions Bot added the lifecycle/merged Lifecycle state: merged label Jul 1, 2026
loganfinney27 added a commit that referenced this pull request Jul 2, 2026
… they stop (#715)

* witness(coding): DRY & WET — the sourced principles, and where they stop

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): address review — gloss markers, literal metaphor glosses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): record the DRY source URL in Provenance (Copilot review)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): add required updated/status frontmatter (Qodo compliance)

Qodo finding #1 (valid, verified against VAULT-METADATA-STANDARD.md §2 required
header fields): add `updated: 2026-07-01` and `status: staged` — the latter
matching every sibling witness leaf (LIVE-STATUS-BOARD-DEDRIFT, TRANSIENT-HEARTS,
BAELNORN). Declined #2 (lowercase tags — lowercasing DRY/WET would re-create the
adjective-vs-principle ambiguity this witness disambiguates; tag standardization
was rejected in #506). #3 (DOCUMENT METADATA footer) flagged for Logan: the
standard requires it but no witness leaf uses it — a standard-vs-genre call
across all witnesses, not one file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): lowercase DRY/WET tags per vault tag convention

VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
loganfinney27 added a commit that referenced this pull request Aug 15, 2026
… they stop (#715)

* witness(coding): DRY & WET — the sourced principles, and where they stop

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): address review — gloss markers, literal metaphor glosses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): record the DRY source URL in Provenance (Copilot review)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): add required updated/status frontmatter (Qodo compliance)

Qodo finding #1 (valid, verified against VAULT-METADATA-STANDARD.md §2 required
header fields): add `updated: 2026-07-01` and `status: staged` — the latter
matching every sibling witness leaf (LIVE-STATUS-BOARD-DEDRIFT, TRANSIENT-HEARTS,
BAELNORN). Declined #2 (lowercase tags — lowercasing DRY/WET would re-create the
adjective-vs-principle ambiguity this witness disambiguates; tag standardization
was rejected in #506). #3 (DOCUMENT METADATA footer) flagged for Logan: the
standard requires it but no witness leaf uses it — a standard-vs-genre call
across all witnesses, not one file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): lowercase DRY/WET tags per vault tag convention

VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
loganfinney27 added a commit that referenced this pull request Aug 15, 2026
… they stop (#715)

* witness(coding): DRY & WET — the sourced principles, and where they stop

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): address review — gloss markers, literal metaphor glosses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): record the DRY source URL in Provenance (Copilot review)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): add required updated/status frontmatter (Qodo compliance)

Qodo finding #1 (valid, verified against VAULT-METADATA-STANDARD.md §2 required
header fields): add `updated: 2026-07-01` and `status: staged` — the latter
matching every sibling witness leaf (LIVE-STATUS-BOARD-DEDRIFT, TRANSIENT-HEARTS,
BAELNORN). Declined #2 (lowercase tags — lowercasing DRY/WET would re-create the
adjective-vs-principle ambiguity this witness disambiguates; tag standardization
was rejected in #506). #3 (DOCUMENT METADATA footer) flagged for Logan: the
standard requires it but no witness leaf uses it — a standard-vs-genre call
across all witnesses, not one file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): lowercase DRY/WET tags per vault tag convention

VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
loganfinney27 added a commit that referenced this pull request Aug 15, 2026
… they stop (#715)

* witness(coding): DRY & WET — the sourced principles, and where they stop

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): address review — gloss markers, literal metaphor glosses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): record the DRY source URL in Provenance (Copilot review)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): add required updated/status frontmatter (Qodo compliance)

Qodo finding #1 (valid, verified against VAULT-METADATA-STANDARD.md §2 required
header fields): add `updated: 2026-07-01` and `status: staged` — the latter
matching every sibling witness leaf (LIVE-STATUS-BOARD-DEDRIFT, TRANSIENT-HEARTS,
BAELNORN). Declined #2 (lowercase tags — lowercasing DRY/WET would re-create the
adjective-vs-principle ambiguity this witness disambiguates; tag standardization
was rejected in #506). #3 (DOCUMENT METADATA footer) flagged for Logan: the
standard requires it but no witness leaf uses it — a standard-vs-genre call
across all witnesses, not one file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): lowercase DRY/WET tags per vault tag convention

VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
loganfinney27 added a commit that referenced this pull request Aug 16, 2026
… they stop (#715)

* witness(coding): DRY & WET — the sourced principles, and where they stop

Written at Logan's direction after he spot-checked whether "DRY" was a grounded
term or an inflated config noun. Records the sourced principles (DRY — Hunt &
Thomas, Pragmatic Programmer 1999; SSOT; WET; and the counter-principles Rule of
Three / Metz / AHA) and the load-bearing boundary the session established:
single-source the FACT, never the INSTITUTION — the unit of DRY is the fact, the
unit of separation is the organ.

Maps the two failure modes to their vault names: under-DRY → drift (the live-
status-board horcruxes, fixed by #708→#709); over-DRY → the Geminiae hivemind
(distinct standings fused to one template). Provenance tiered: DRY core
corroborated by the Wikipedia page Logan supplied; adjacent citations flagged
verify (a confabulated cite would be self-refuting here). The check that
occasioned it is witnessed as the point — the loop, not being right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): address review — gloss markers, literal metaphor glosses, consistent terms

Sourcery review on #715 (clarity, apt for a legibility-focused witness):
- add a provenance-tier legend at first use ([fact]/[research]/[mapping])
- literal glosses for the lore metaphors: "one underlying agent reused as
  several bodies"; Geminiae hivemind = "one underlying model masquerading as
  many distinct standings"
- standardize the term-pair on fact vs. institution (dropped stray
  "things"/"organ") with an inline definition

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): record the DRY source URL in Provenance (Copilot review)

Copilot (line 110) correctly flagged that the Provenance section cited "the
Wikipedia article Logan supplied" without the URL — an auditability gap in a
witness whose purpose is provenance. Recorded the concrete link
(https://en.wikipedia.org/wiki/Don't_repeat_yourself) so a future reader can
re-check the source without external context.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): add required updated/status frontmatter (Qodo compliance)

Qodo finding #1 (valid, verified against VAULT-METADATA-STANDARD.md §2 required
header fields): add `updated: 2026-07-01` and `status: staged` — the latter
matching every sibling witness leaf (LIVE-STATUS-BOARD-DEDRIFT, TRANSIENT-HEARTS,
BAELNORN). Declined #2 (lowercase tags — lowercasing DRY/WET would re-create the
adjective-vs-principle ambiguity this witness disambiguates; tag standardization
was rejected in #506). #3 (DOCUMENT METADATA footer) flagged for Logan: the
standard requires it but no witness leaf uses it — a standard-vs-genre call
across all witnesses, not one file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd

* witness(coding): lowercase DRY/WET tags per vault tag convention

VAULT-CONVENTIONS.md requires lowercase tags; DRY/WET were the only
uppercase entries in this note's tags list.

Claude-Session: https://claude.ai/code/session_01HismCgmXWnAWg4362xJ3vj
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/merged Lifecycle state: merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants