Skip to content

Incorporate Sightline calibration feedback #18

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
Charlie-Wang-03 merged 2 commits into from
Oct 1, 2026
Merged

Incorporate Sightline calibration feedback #18

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
96b73fd
Preserve unknown states and scoped disclosure
Charlie-Wang-03 Oct 1, 2026
c8c1d9c
Record compatibility identities for external semantics
Charlie-Wang-03 Oct 1, 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
4 changes: 4 additions & 0 deletions docs/preferences.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ For agent-generated or large-scale changes, tests, validation commands, runtime

Separate execution status from domain acceptance whenever that distinction materially affects correctness. A command, pipeline, training run, build, or API call completing successfully should not automatically imply that the resulting scientific, data-quality, business, or engineering acceptance criteria passed.

Preserve meaningful unknown states. Unavailable, unobserved, indeterminate, or not-yet-verified evidence should not be collapsed into absence, failure, incompatibility, or zero unless the system can actually establish that conclusion.

Verification effort should remain proportional to the project's risk.

## 3. Reversible over Unnecessarily Risky
Expand Down Expand Up @@ -50,6 +52,8 @@ Reason about the actual trust boundary rather than treating “local” as synon

Use the least access necessary, keep private and public artifacts intentionally separated, and inspect repository history before making previously private material public when that history may contain sensitive information.

A canonical internal representation does not require every consumer to receive the same disclosure surface. When trust, purpose, or data sensitivity differs, expose only the subset appropriate to that consumer while keeping the projection's provenance and omissions explicit.

## 7. Portability and Locality Are Means, Not Goals

Prefer replaceable boundaries or local execution when they provide concrete value in privacy, reproducibility, autonomy, maintenance, cost, testing, or future flexibility.
Expand Down
2 changes: 2 additions & 0 deletions docs/project-conventions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,8 @@ Use stronger validation for higher-risk work; do not add machinery whose mainten

Validation should protect actual project claims and important risks rather than pursue arbitrary completeness. If a project publicly claims support for particular platforms, runtimes, artifact properties, compatibility boundaries, or quality guarantees, its validation surface should cover those claims when practical.

When behavior depends on fast-moving external tools, APIs, schemas, or documented semantics, record the authority and compatibility identity that the implementation was validated against. Useful identities may include a version, commit, documentation date, API generation, schema revision, or another reviewable reference.

Automate only properties that are genuinely machine-verifiable. Keep explicit human gates for judgments that remain experiential, aesthetic, ethical, editorial, or otherwise non-deterministic. A green automated check should not be used to imply that a human-only quality judgment has been proven.

## Agent Context
Expand Down
Loading