House Opinions¶

The repository owner's own opinions: preferences earned from experience rather than traced to a vetted source. They are first-class but always visibly marked, so a reader (human or agent) can tell "the community's best practice" from "how we do it here".

How this works¶

1. The owner adds an entry to the Inbox below. A sentence or two is enough; the rationale matters more than polish.
2. The weave-house-opinion skill weaves it in: the opinion lands in the right opinions/ file (and templates/ where applicable) with house in the file's sources: frontmatter, and the inbox entry moves to Woven with a link.
3. The marking is a fixed literal. Every house opinion is prefixed with the exact string **House:** (bold, colon inside), machine-checkable via grep -F '**House:**'. The house id and the marking always travel together: one without the other is an audit finding.
4. House beats roster on conflict (canonical statement; other files point here): if a house opinion contradicts a sourced one, the house opinion wins and the sourced position is kept as a one-line "the community default is X (source); we do Y because Z" note, citing the source. Harvest, refresh, and audit runs must never remove, dilute, or un-mark house content.
5. External contributors propose opinions via pull request: see the PR template. An experience-based contributor opinion the owner accepts is woven by adoption: the owner takes responsibility for it as a house opinion, and the contributor and PR are credited in the Woven table's Provenance column.

The house source id is reserved and documented in AWESOME-HUMANS.md; its authority is repository ownership, so it is exempt from the admission criteria, which is why it must stay visibly marked wherever it is used.

Entry format¶

### <short title>

- **Opinion:** <what to do, one sentence>
- **Why:** <the experience or reasoning behind it>
- **Scope:** <which topic/file it belongs to, if known>

Inbox¶

Nothing waiting.

Woven¶