Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 3 additions & 0 deletions DISCOVERY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# Discovery: organvm/dot-github--logos

Value thesis: `organvm/dot-github--logos` is not an archival logo/nameplate repository; it is the live public-process control surface for ORGAN-V. Its real exports are the GitHub-rendered organization profile, community-health defaults, issue and PR intake templates, repository-dispatch receiver, weekly health heartbeat for sibling Logos pipelines, distribution experiment record, signal-triage ritual, and external-validation/revenue ledgers. The highest latent value is a reusable public-process operating layer for the estate: it turns essays and repo traffic into auditable contributor feedback, community participation, consult/revenue paths, and pipeline-health alerts without inventing a new app. Promote it as infrastructure; the best first concrete task is to close the stale W14 top-of-funnel reach loop by adding a reach ledger or issue template that records source, action, owner, target date, and shipped link, then update `docs/signals-triage/triage-log.md` so reach remediation is tracked with the same SLA discipline as conversion fixes.
15 changes: 15 additions & 0 deletions value-repos.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
{
"schema_version": "1.0",
"description": "Repos promoted into the ranked value tier - discovered to hold concrete, build-out-worthy latent value.",
"ranked": [
{
"repo": "organvm/dot-github--logos",
"promoted": "2026-07-01",
"source": "auto-discovery",
"tier": "infrastructure",
"value": "Live public-process control surface for ORGAN-V: org profile, community-health defaults, intake templates, pipeline heartbeat, distribution experiment record, signal triage ritual, and external-validation/revenue ledgers.",
"first_task": "Close the stale W14 top-of-funnel reach loop by adding a reach ledger or issue template that records source, action, owner, target date, and shipped link, then update docs/signals-triage/triage-log.md so reach remediation is tracked with the same SLA discipline as conversion fixes.",
"thesis": "DISCOVERY.md"
}
]
}