Skip to content

How it works

Agent skills maintain each ecosystem's repository, and nothing becomes an opinion without passing CI and the owner's review. The diagrams below are an overview. Where one disagrees with a skill or the admission criteria, follow the skill or the criteria.

Every change is a pull request

Each skill works on its own branch, and its changes land through a pull request. CI checks the metadata on every opinion and template, that every cited source is on the roster and citable, and that every link resolves. The owner then reviews and merges it.

Two skills only report: audit-freshness finds stale review dates and lagging version pins, and review-project grades an external codebase against the opinions. Their findings, a scheduled release watch, and a monthly harvest reminder start the next run.

Maintenance pipelineSwimlane diagram of how an ecosystem's repository maintains itself: vet-source, research-topic, resolve-research, harvest-sources, the version refresh, and weave-house-opinion each work on their own branch, pass CI and the owner's review, and land in the roster, research/ or the opinions and templates; audit-freshness and review-project only report. Their findings, the release watch and the harvest reminder start the next run.lanepicks upskillagent gatehuman gatelands inSourcesResearchOpinionsReportscandidate source,or a change in standingvet-sourcevet/<source-id>CI: metadata,sources, linkscheck evidencea questionabout <topic>research-topicresearch/<topic>CI: metadata,sources, linksreviewtopic saved inresearch/resolve-researchresolve/<topic>CI: metadata,sources, linksapprove weavemonthly harvestreminder issueharvest-sourcesharvest/<date>CI: metadata,sources, linksreviewrelease-watch PR,or a newer pinversion refreshrefresh/<version>CI: metadata,sources, linksreviewHOUSE-OPINIONS.mdinbox entryweave-house-opinionhouse/<slug>CI: metadata,sources, linksconfirm wordingperiodic cadenceaudit-freshnessreport onlyno pull requesta project pathor repository URLreview-projectreport onlyno pull requestAWESOME-HUMANS.mdthe rosterresearch/staged, unresolvedopinions/templates/what good looks likea reportnever saved herefindingsWhat starts a runfindings, the release watch, the harvest reminder, youstarts the next skill

Sources need a track record

A source joins the roster on its track record: at least two years of sustained writing, with depth, accuracy, and an independent view. A source with less than two years, or dormant for over a year, goes on the watch list, which supplies leads but is never cited. A source is vetted again when it goes quiet or a blocker clears.

Two markings limit how an opinion can cite a roster source, and CI enforces both:

  • Corroborate: a long track record but thin depth. An opinion can cite the source, but every claim it supports also needs an unmarked source.
  • Discovery-only: an aggregator, such as a newsletter or a curated list of links. It's never cited, and an opinion cites the primary source it leads to instead.
Source standingFlow diagram: vet-source sorts a candidate source into citable, with two years of writing and all four criteria; the watch list, under two years or dormant; or declined. A citable source is unmarked, marked Corroborate and never the only citation on a claim, or marked Discovery-only and never cited. Citable and watch-listed sources go back through vet-source when they go dormant, drop in quality, or clear a blocker.Candidate sourceblog, docs, book, newslettervet-sourcecriteriaCitablequotable in opinions and templates, within its markingunmarkedmay carry a claim alone**Corroborate.**cited, never as the only source on a claim**Discovery-only.**never cited, only followed to its primary sourceWatch listleads only, never citedDeclinedoff the roster, the decision loggedtwo years and all four criteriaunder two years, or dormantotherwisedormant, weakerblocker clearsre-vetted: standing is never permanent

Research is staged, never merged in place

A research topic saves the evidence on a subject in its own pull request. A second pull request then promotes it into the opinions and templates, or discards it, and deletes the topic either way. A topic on disk is unresolved.

Research lifecycleFlow diagram: research-topic opens a pull request that saves research/<topic>.md; resolve-research then promotes it into the opinions and templates, discards it, or promotes part of it, deleting the topic in the same pull request. A blocked remainder stays staged and goes back through resolve-research once vet-source clears the source it waits on.research-topiccited, on research/<topic>PR mergesresearch/<topic>.mdon record, unresolvedresolve-researchown PRPromoteopinions and templates updated, topic deletedDiscardnothing woven, topic deletedPartial promotionthe rest woven, the blocked remainder stays stagedonce vet-source clears its source

House opinions

House opinions are preferences from experience, which no vetted source backs. Each belongs to a house profile, owned by a person or an organisation. The site shows none by default, so every page is sourced community practice. Choose a profile in the header to see its house opinions, each marked House: beside the sourced text it changes. For how profiles work, including private ones for your own organisation, see House profiles.