agenticsorg / agenticsorg/community-projects
OIA Application Matrix (v0) — feedback & refinement
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
What this is
A v0 OIA Application Matrix is now published on the committee dashboard:
https://agenticsorg.github.io/community-projects/oia-matrix.html
It maps each application to the OIA 10-layer stack (L0–L9) + 6 spans (security, sovereignty, auditability, energy, identity, provenance), with per-row evidence tiers, inline drill-downs, a gap-closing improvement-prompt generator, and a client-side repo "retest" scan. It is intended to structure the OIA intake discussion — a strawman for committee red-lining, not an official ranking.
This issue is the feedback channel
The page links here. Please use the comments to propose corrections and refinements. Specifically useful:
- Placement corrections — a layer/span assignment that's wrong or overstated (the page flags
lean-agenticas one such case where code contradicted the description). Independent re-tagging by a second member is the cheapest way to move rows fromdesctocode ✓. - The tagging rubric — a 1-page layer/span rubric with 1–2 anchor examples per layer, so classification is reproducible rather than one person's read.
- Weights — whether/how to add a composite score. Deliberately omitted in v0 because weighting the 12 dimensions is a committee decision, and a single number would launder that judgment.
- New submissions — repos that belong in the matrix. (Recent adds:
proffesor-for-testing/agentic-qe,ohdearquant/lionagi.) - Funnel wiring — how the matrix plugs into intake (metaharness
scoreas the mechanical Stage-2a gate; layer/span footprint as Stage-2b).
Next steps (from the analysis)
- Adopt the layer-footprint matrix as the standard submission artifact.
- Wire
metaharness scoreinto intake Stage 2a. - Draft the 1-page layer/span tagging rubric (anchor examples).
- Run the first live submission through both and compare the auto report card to a human read.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the published OIA Application Matrix at agenticsorg.github.io/community-projects/oia-matrix.html and review the issue comments for proposed corrections. Compare layer/span placements, the tagging rubric, weighting, new submissions, and funnel wiring against the listed next steps. Done means the committee has agreed on refinements and documented the resulting matrix and intake decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100