docs: settle the contributor-identity scheme (harness@host / operator:name) #113
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/contributor-identity-decision"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Settles the contributor-identity scheme so it stops resurfacing, and enforces it at the point where hostname facts are collected.
Decision (Jev probes)
<harness>@<host>(e.g.zot@debby)operator:<name>(e.g.operator:sam)human:*,opus-*,pi-*) grandfatheredWhy
operator:(nothuman:)Adding
operator:<name>to the option set moved Jev's pick fromname_only0.56 →operator_prefix0.89 (human_prefix 0.11, name_only 0.00). "operator" is already the repo's word for the human role;human:is a species marker that leaked into 96 frontmatter entries.Fit with the hostname-facts step (
host-inventory-observation.v1)The envelope already carries both halves —
collector_identityandobserved_host_identity.hostname— so the rule is deterministic:scripts/tests/test_identity_host.pyenforces it (runs under the existingpython-testsjob +ci-checks.sh). It failed on the contract's ownhermes-openaiexample before the fix — the drift was sitting in the doc that defines it.Changes
scripts/tests/test_identity_host.py— new deterministic check (table-driven negatives: no-host, FQDN, agreed_name, wrong host, uppercase, legacyhuman:) + a doc-fixture assertion.docs/plans/SYSTEM1-WIKI-INVENTORY.md— examplecollector_identity: "hermes-openai"→hermes@debby.AGENTS.md—verified_byschema row + note on the identity format.docs/wiki/naming-decisions.md— new Contributor identity ledger entry.docs/wiki/abbreviations.md—FQDN(wiki-lint required it).docs/evidence/contributor-identity-decision/— both Jev probes, results, raw responses, README.Scope / non-goals
Canonical agent-and-host identity stays deterministic and outside Jev (jev-triage safety boundary). Corpus-wide enforcement is deliberately deferred until the legacy allowlist is settled — only the format rules and the contract example are enforced here. Weak probe answers (
scope0.48,enforcement0.55,record_location0.49) are taken as the conservative defaultsmetadata_only/advisory/ ledger+AGENTS.md.Gates
check-formatpass ·check-dates --strictclean ·wiki-lint --strictclean (762/0) · python-tests OK incl. the new test ·check-okfadvisory exit 0.