Harness Intelligence Wiki
Grilling

Opensrc Knowledge Refactor Grill Status

Opensrc Knowledge Refactor Grill Status

Branch Dashboard

BranchCompletionLocked directionStill open
Opensrc Context Model100%Add curated example repositories as maintained framework-pack metadata in apps/cli/src/data/catalog/packs.ts; do not let scaffold setup invent arbitrary repos.None.
Effect Pack Example Repositories100%Seed curated repos with minimal metadata; versions come from cloned repo manifests; inclusion is manual pack-maintainer curation.None.
Scoped AGENTS.md Guidance100%Emit explicit opensrc guidance for selected-pack curated examples in generated workspace/scoped prompts; keep root shared guidance generic.None.

Parked Branches

  • Non-Effect framework packs: preserved for later unless the current grill expands beyond Effect as the first implementation slice.

Glossary

Terms

  • Framework Pack: A detected or selected scaffold pack that bundles skills, prompt guidance, hooks, and related knowledge for a framework or technical surface. Avoid: raw skill list, loose framework docs.
  • Package Source Context: The direct upstream package/library source inspected with opensrc path <package> or an equivalent upstream repository path. Avoid: example repo.
  • Example Repository Context: A curated real-world repository inspected with opensrc path owner/repo to learn applied framework patterns beyond the package source itself. Avoid: package source, random sample repo.
  • Pack Mapping: The association between an example repository and a framework pack, represented as { uid, version }.

Relationships

  • Example Repository Context belongs to one or more Framework Packs.
  • Package Source Context and Example Repository Context are separate opensrc contexts.
  • Example Repository Context has one or more Pack Mappings.
  • Framework Pack owns its curated Example Repository Context metadata in the pack catalog.

Axioms

  • Agents must not guess framework behavior when official docs or source context can answer it.
  • Curated example repositories should guide applied pattern research, not replace official docs or package source inspection.
  • Scaffold setup must not invent or auto-select arbitrary opensrc repositories, but framework packs may declare curated example repositories as maintained pack knowledge.
  • Example repository entries stay minimal; generic pack guidance explains that they are evidence sources for real-world patterns and code architectures aligned to the pack's included skills.
  • Curated example repository versions should be read from the cloned repositories' package manifests; do not model unknown versions by default.
  • Example repository inclusion is a maintainer curation decision, not a validation gate over every included skill.

Flagged Ambiguities

  • "opensrc context" may mean direct package source or curated real-world examples. Resolution: model both as separate contexts.
  • "preselect concrete opensrc repositories" conflicts with the proposed curated framework-pack repositories. Resolution: arbitrary repo selection remains forbidden; curated pack-maintained repositories are allowed.

On this page