Name the founder instead of "the operator" in repo-owned prose
The agent environment orientation (§8) reserves "operator": Operator is a CARING lifecycle role and OPERATE is an Auth Mode, so the founder's decisions are written as the founder exercising GOVERN @ estate. Only authorization references changed. The canon's own domain use of operator — CARING roles, network operators, operator hours — is correct and untouched, as are preserved seeds, assimilation sources, history records and consumer-authored feedback. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 121421@bnt-lap001 Assistant-Session: 36f8657c-ebfa-4a2e-9ba0-bff06738f233
This commit is contained in:
parent
5cd7728366
commit
3efe5c27e1
3 changed files with 10 additions and 10 deletions
|
|
@ -13,8 +13,8 @@
|
|||
## Demand signal
|
||||
|
||||
The first source-owned declaration came from a source that can emit only while
|
||||
an attended process runs: `local-identity serve`, plus operator-invoked CLI
|
||||
commands. For such a source, silence has two meanings. Silence while the
|
||||
an attended process runs: `local-identity serve`, plus attended CLI
|
||||
invocations. For such a source, silence has two meanings. Silence while the
|
||||
process runs may be a finding. Silence while the process is not running
|
||||
carries no information. The contract cannot tell the two apart:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue