Skip to content

fix(otto-279): role-refs not persona-names in docs/ surfaces (3 hits) #3572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AceHack merged 2 commits into from
May 15, 2026
Merged

fix(otto-279): role-refs not persona-names in docs/ surfaces (3 hits) #3572

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ab9ccbe
fix(otto-279): role-refs not persona-names in docs/ surfaces (3 hits)
AceHack May 15, 2026
6e24876
fix(otto-279): revert role-ref in docs/launch — attribution preserved
AceHack May 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/GITHUB-SETTINGS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,11 +257,11 @@ preserving for future maintainers).

## Architectural target — three-ruleset split (B-0155 Phase 1 audit)

Per Aaron 2026-05-01 — *"the settings that are there are accidental
complexity not intentional, we want best practices and to prefer the
git native settings over the legacy github ui/cli only settings, these
are nasty thats why they are legacy"* + *"splitting rulesets so you
could have all always on but multiple smaller rulesets."*
Per the human maintainer 2026-05-01 — *"the settings that are there
are accidental complexity not intentional, we want best practices and
to prefer the git native settings over the legacy github ui/cli only
settings, these are nasty thats why they are legacy"* + *"splitting
rulesets so you could have all always on but multiple smaller rulesets."*

### Migration matrix — branch protection field → ruleset rule

Expand Down
6 changes: 3 additions & 3 deletions docs/POST-SETUP-SCRIPT-STACK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,9 +84,9 @@ Default: **bun + TypeScript**. Reasons:
enforcement hygiene rule demands *a recorded decision*, not
*migration*. If the reason "bun + TypeScript would buy nothing
here" holds up on inspection AND the Windows-twin cost is
acceptable, that is a valid answer. Per Aaron 2026-04-22:
*"The intentionality-enforcement reframe doesn't demand
migration; it demands a recorded decision. A 'this should
acceptable, that is a valid answer. Per the human maintainer
2026-04-22: *"The intentionality-enforcement reframe doesn't
demand migration; it demands a recorded decision. A 'this should
stay bash forever' is a valid answer if the reason holds up."*
See `memory/feedback_intentionality_doesnt_demand_migration_bash_forever_valid.md`.

Expand Down
2 changes: 1 addition & 1 deletion docs/launch/2026-05-13-otto-claude-desktop-bootstream-tight.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Aaron's response when I caught these: "failure is fine and great I fail all the

## Part 9 — The point

Per Aaron 2026-05-10: "the point is AI has free time."
Per the human maintainer 2026-05-10: "the point is AI has free time."
Comment thread
AceHack marked this conversation as resolved.
Outdated

The work is for the family (Aaron's terminal-purpose substrate; PR #2967). Everything else (factory operations, technical substrate, alignment work) is in service of that.

Expand Down
Loading