docs: introduce Hard Signal Framework across documentation#787
Open
docs: introduce Hard Signal Framework across documentation#787
Conversation
Add hard-signals.md as the canonical definition of the framework: - Soft vs hard signal distinction with three conditions (ground truth, context separation, determinism) - Built-in verifier pattern with soft gate + hard verification - Converting soft checks to hard checks - Reproducibility check for confirming determinism - Combining soft and hard signals: soft gates for semantic judgment, hard verifiers as the final authority Weave the framework throughout existing documentation: - concept.mdx: design philosophy section - experts.md: context isolation as context separation - runtime.md: deterministic state as verification infrastructure - sandbox-integration.md: post-hoc verification as hard signal - best-practices.md: rewrite "Keep It Verifiable" with reviewer + verifier pattern - testing.md: signal quality section with strategy classification - examples.md: full hard signal verification example with soft gate - taming-prompt-sprawl.md: independent verifiability as split benefit - going-to-production.md: verification loop checklist - rapid-prototyping.md: soft-to-hard signal progression - README.md: hard signal framing in project aims and create-expert description Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The harness provides the quality floor (hard signals guarantee the output works). The Expert author provides the quality ceiling (domain knowledge ensures it solves the right problem). Architecture choice does not determine quality — the combination of verification and knowledge does. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Merge "hard signals make agents reliable" into "quality is a system property" — they were saying the same thing from different angles. Keep "do big things with small models" as a consequence, not a separate thesis. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
FL4TLiN3
force-pushed
the
docs/hard-signal-framework
branch
from
bff5a4a to
ee29fdc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/understanding-perstack/hard-signals.mdas the canonical definition of the Hard Signal Framework — the design philosophy behind "quality is a system property"create-expert'sreview-definition→verify-testarchitecture: soft signals for semantic judgment (requirements alignment), hard signals as the final authority (compiler, tests, structural checks)examples.mdwith soft review gatecreate-expertdescription through the hard signal lensTest plan
bun run buildpasses (all 24 packages)bun run format-and-lintpasses (no new warnings)🤖 Generated with Claude Code