Date: 2026-10-05 Source: hermes-cron-log Slack thread https://ryevalley.slack.com/archives/C0BMPHWFS0H/p1791209783303749 Proposed by: Hermes (Otter notes cron) Approved by: Michael Houck
Boundary
Do not reference Bargain Paradise (the Amazon roll-up Adam’s company acquired from a seller named Trent), the counterparty (Trent), or any detail of the active dispute. Same treatment as existing FLAG LEGAL matters.
Context
Hermes flagged this as a boundary candidate after mining Adam’s Otter meeting notes (week of 2026-09-28). The situation: there is an active legal/commercial dispute at Bargain Paradise with the original seller (Trent) - inconsistent diligence numbers, a forced PO, seller note overcharges, and plans to pull inventory from his warehouse and factory as a defensive move. Adam told his team to be prepared for a fight.
Michael replied: “yes I think your boundary candidate is a good idea” - approving the standing rule.
Standing Rule
Never reference in Adam’s content or any team-facing context:
- Bargain Paradise acquisition
- Trent (the counterparty seller)
- Any detail of the dispute (diligence numbers, PO, seller note, inventory pull plans)
This rule is NOT yet written to adam-gillman/client-context.md or rule-card.json. Per canon, those files are human-gated. Michael’s approval here is sufficient to treat this as active. An account lead should formally apply it to the rule-card when next updating Adam’s client files.
Action Needed
- Account lead (Blake Stewart or Michael) to write this to adam-gillman rule-card.json.
- Flag to Blake so he is aware before next content batch.