docs(positioning): align README + ADRs + specs to Pindrop red lines #28

Merged

alee merged 1 commits from docs/positioning-cleanup into main 2026-07-10 02:19:49 +00:00

Conversation 0 Commits 1 Files Changed 21 +130 -71

alee commented 2026-07-09 23:15:58 +00:00

Owner

Copy Link

What lands

• 21 markdown files reframed to draw the voice-security scope boundary explicitly: rutster integrates with dedicated voice-security vendors via the agent tap; it does not compete with them. Caller authentication, fraud detection, voice biometrics, spoof / liveness / deepfake detection are now stated as deliberately out of scope in README, ARCHITECTURE.md, PORT_PLAN.md, and ADRs 0002/0008/0009.
• Terminology realigned across README, AGENTS.md, all ADRs, ARCHITECTURE.md, PORT_PLAN.md, CONTRIBUTING.md, all 5 slices' specs/plans, all 4 review docs:
  • 'Security-as-product' -> 'Trust & operational safety'
  • 'toll-fraud controls' -> 'spend guardrails'
  • 'in-boundary spend/abuse' -> 'in-boundary spend guardrails'
  • 'Security-constitutive' FOB -> 'boundary-constitutive'
  • 'spend/abuse gate' (ADR-0009)-> 'spend gate'
• Headline retains 'AI-native' (part of the wedge per the positioning doc's own competitive-landscape conclusion) and adds 'inspectable'.
• Rename pointers ('formerly X') left in ADR-0002 and ADR-0009 for future readers.

Why

Pre-empts a Pindrop conflict-of-interest surface before any public
positioning of the project. The voice-security red lines are now
explicitly framed as a load-bearing scope boundary (not a gap);
the positioning doc itself remains the working source of truth at
repo top-level untracked.

Notes

• Docs-only -- no code, no Cargo.toml, no CI yaml. Pre-existing cargo fmt/clippy/test gates on cc25e80 remain unaffected.
• 1 commit, DCO-signed (Aaron D. Lee himself@adlee.work).
• Default squash-merge.
• The Rutster -> Harken rename is explicitly deferred (separate multi-day lift; not in this PR).

## What lands - 21 markdown files reframed to draw the voice-security scope boundary explicitly: rutster integrates with dedicated voice-security vendors via the agent tap; it does not compete with them. Caller authentication, fraud detection, voice biometrics, spoof / liveness / deepfake detection are now stated as deliberately out of scope in README, ARCHITECTURE.md, PORT_PLAN.md, and ADRs 0002/0008/0009. - Terminology realigned across README, AGENTS.md, all ADRs, ARCHITECTURE.md, PORT_PLAN.md, CONTRIBUTING.md, all 5 slices' specs/plans, all 4 review docs: - 'Security-as-product' -> 'Trust & operational safety' - 'toll-fraud controls' -> 'spend guardrails' - 'in-boundary spend/abuse' -> 'in-boundary spend guardrails' - 'Security-constitutive' FOB -> 'boundary-constitutive' - 'spend/abuse gate' (ADR-0009)-> 'spend gate' - Headline retains 'AI-native' (part of the wedge per the positioning doc's own competitive-landscape conclusion) and adds 'inspectable'. - Rename pointers ('formerly X') left in ADR-0002 and ADR-0009 for future readers. ## Why Pre-empts a Pindrop conflict-of-interest surface before any public positioning of the project. The voice-security red lines are now explicitly framed as a load-bearing scope boundary (not a gap); the positioning doc itself remains the working source of truth at repo top-level untracked. ## Notes - Docs-only -- no code, no Cargo.toml, no CI yaml. Pre-existing cargo fmt/clippy/test gates on cc25e80 remain unaffected. - 1 commit, DCO-signed (Aaron D. Lee <himself@adlee.work>). - Default squash-merge. - The Rutster -> Harken rename is explicitly deferred (separate multi-day lift; not in this PR).

alee added 1 commit 2026-07-09 23:16:01 +00:00

docs(positioning): align README + ADRs + specs to Pindrop red lines ... a2c5f5952d

Reframes the public-facing positioning to draw the voice-security
scope boundary explicitly. Rutster integrates with dedicated
voice-security vendors via the agent tap; it does not compete with
them. The four Pindrop red-line surfaces (caller authentication,
fraud detection, voice biometrics, spoof / liveness / deepfake
detection) are now stated as deliberately out of scope in README,
ARCHITECTURE.md, PORT_PLAN.md, and ADRs 0002/0008/0009.

Terminology realigned across 21 repo files:
  - 'Security-as-product'        -> 'Trust & operational safety'
  - 'toll-fraud controls'        -> 'spend guardrails'
  - 'in-boundary spend/abuse'    -> 'in-boundary spend guardrails'
  - 'Security-constitutive' FOB -> 'boundary-constitutive'
  - 'spend/abuse gate' (ADR-0009)-> 'spend gate'

In-boundary spend guardrails = carrier-cost + pacing abuse prevention
(unauthorized outbound calls, per-call spend caps, dialer pacing) --
NOT caller-side fraud detection. This distinction is now load-bearing
in README, ADR-0002, ADR-0008, ADR-0009, ARCHITECTURE.md, PORT_PLAN.md.

Headline retains 'AI-native' (part of the wedge per the positioning
doc's own competitive-landscape conclusion) and adds 'inspectable'.

Rename pointers ("formerly X") left in ADR-0002 and ADR-0009 for
future readers; the positioning source doc itself is untouched.

No code, no Cargo.toml, no CI yaml -- docs only. Pre-existing
cargo fmt/clippy/test gates on cc25e80 remain unaffected.

Signed-off-by: Aaron D. Lee <himself@adlee.work>

alee referenced this pull request 2026-07-09 23:50:26 +00:00

fix(deploy-epoch): un-spoofable smoke gates + honest docs (deploy-epoch-fix) #29

alee merged commit 83264c456e into main 2026-07-10 02:19:48 +00:00

alee referenced this issue from a commit 2026-07-10 02:19:51 +00:00

docs(positioning): align README + ADRs + specs to Pindrop red lines (#28)

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

alee

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: alee/rutster#28