What
Tighten the semantics around runtime artifacts and governance metrics so the public surface matches actual behavior.
Motivation
Recent launch hardening improved the README, but two areas still deserve explicit follow-up:
workspace/ artifacts are created relative to the current working directory when users run ac- governance score labels such as
epistemic_honesty and constitutional_compliance are still partly proxy metrics rather than direct measurements of the named concepts
Scope
- review
workspace/ path handling and decide whether to keep CWD-relative behavior or anchor it more explicitly
- document the chosen behavior in README and CLI help
- review governance score dimension names and descriptions
- tighten wording where a metric is really format/process compliance rather than substantive governance quality
- add tests for any changed path behavior or renamed metrics
Why this matters
This is mainly a trust and clarity issue. The project is stronger when runtime behavior, metric names, and public docs tell the same story.
What
Tighten the semantics around runtime artifacts and governance metrics so the public surface matches actual behavior.
Motivation
Recent launch hardening improved the README, but two areas still deserve explicit follow-up:
workspace/artifacts are created relative to the current working directory when users runacepistemic_honestyandconstitutional_complianceare still partly proxy metrics rather than direct measurements of the named conceptsScope
workspace/path handling and decide whether to keep CWD-relative behavior or anchor it more explicitlyWhy this matters
This is mainly a trust and clarity issue. The project is stronger when runtime behavior, metric names, and public docs tell the same story.