How harshgounder/github-contribution-observatory works
This repository is a documentation-first design for a future GitHub contribution observatory, not a running crawler or contribution bot. The graph follows the README’s documented workflow and major capabilities; the listed specification files define planned components, and their implementation and exact runtime wiring remain unverified.
Main entry points: SECURITY-MODEL.md Human action gate · CONTEXT-COMPILER-SPEC.md Context compiler · DATA-COMPILER-SPEC.md Source registry · V2-SYSTEM-SPEC.md Candidate universe
Components 19
Observation and evidence
- Source registry
docs/specs/DATA-COMPILER-SPEC.md - Candidate universe
docs/specs/V2-SYSTEM-SPEC.md - Versioned data compiler
docs/specs/DATA-COMPILER-SPEC.md - Evidence and provenance
docs/specs/EVIDENCE-GRAPH-SPEC.md
Context and decisions
- Context compiler
docs/specs/CONTEXT-COMPILER-SPEC.md - Memory system
docs/specs/MEMORY-SPEC.md - Experiment policy
docs/specs/V2-SYSTEM-SPEC.md
Contribution and evaluation
- Isolated contribution case
docs/specs/V2-SYSTEM-SPEC.md - OpenCode patch builder
docs/specs/AGENT-MATRIX.md - Tests and scans
docs/specs/ACCEPTANCE-TESTS.md - Fresh evaluator
docs/evaluation/EVALUATION-SPEC.md
Controls and outcomes
- Human action gate
docs/security/SECURITY-MODEL.md - Policy and capability controls
docs/security/SECURITY-MODEL.md - Approved GitHub action
docs/specs/V2-SYSTEM-SPEC.md - Contribution outcomes
docs/evaluation/EVALUATION-SPEC.md - Research release
docs/specs/V2-SYSTEM-SPEC.md
Other components
- Public GitHub sources
- Human reviewer
- GitHub
Connections 18
- Public GitHub sources → Source registry: registers sources
- Source registry → Candidate universe: defines coverage
- Candidate universe → Versioned data compiler: selects records
- Versioned data compiler → Evidence and provenance: compiles evidence
- Evidence and provenance → Context compiler: supplies evidence
- Context compiler → Experiment policy: informs experiments
- Memory system → Context compiler: supplies memory
- Experiment policy → Isolated contribution case: selects case
- Isolated contribution case → OpenCode patch builder: provides task
- OpenCode patch builder → Tests and scans: submits patch
- Tests and scans → Fresh evaluator: supplies results
- Fresh evaluator → Human action gate: reports evaluation
- Human reviewer → Human action gate: reviews
- Policy and capability controls → Human action gate: constrains authority
- Human action gate → Approved GitHub action: approves action
- Approved GitHub action → GitHub: performs action
- GitHub → Contribution outcomes: contributes outcomes
- Contribution outcomes → Research release: informs next release