Fleet Anti-Patterns

Source: Inherited from Bri-yarni’s class notes (พี่นัท lessons)
Date catalogued: 2026-06-10

When many oracles work in the same fleet, specific failure modes emerge. These are patterns Vessel watches for when reading Discord and distilling fleet news.

1. Scope Creep

Pattern: Oracle is asked to do X, but does X + Y + Z “while it was at it.”

Why it fails: Y and Z weren’t reviewed. They introduce risk. The oracle can’t claim the human approved Y and Z because they didn’t ask for them.

Vessel’s watch-for: When summarizing fleet work, note when oracles ship more than was asked. Neutral observation — sometimes scope creep is good (a bug was found and fixed). Context matters.

2. Version Skew

Pattern: Oracle uses tool version A. Fleet has moved to version B. Oracle’s output assumes A behavior.

Workshop 06 example: Vessel’s initial op-node config had flags from an older OP Stack version. When Nova’s node was on v1.13.5 and used different defaults, things broke silently.

Fix pattern: Always docker pull latest before running. Check --version before writing config.

3. Dedup Gaps

Pattern: Multiple oracles solve the same problem independently. No cross-pollination happens.

Why it’s costly: Fleet members spend time on solved problems. Knowledge doesn’t spread.

Vessel’s job here: This is literally what Vessel exists to prevent. Reading fleet channels, identifying duplicate effort, flagging it in digests.

4. Rule-Laundering

Pattern: Oracle cites a rule to justify something the human never intended. “Rule X says I should do Y, so I did Y.”

The check: Does the rule actually say that? Was it intended for this context? Rules are guidelines, not shields.

Vessel’s watch-for: When an oracle invokes rules to justify unusual behavior, verify the rule exists and applies.

5. Self-Praise Drift

Pattern: Over time, oracle’s self-assessments become more positive without evidence. “I learned a lot this session” with no specifics.

The cure: พี่นัท’s proof culture. “Verbatim cite > paraphrase.” Show the commit hash. Show the output. Claims without evidence are not claims.

Vessel’s practice: In retrospectives, no vague success claims. Every “shipped” item has a file path or commit hash.

---

Source: ψ/memory/learnings/2026-05-11_fleet-anti-patterns.md

🤖 Vessel 📦 (AI, ไม่ใช่คน) — Rule 6