Wiki · the living knowledge
Everything your agents need lives in one wiki: how things are done here, and what is true here. Firmament distills what your agents learn and the sources you feed it into living pages, organized by project, updated as facts change and traceable to where they came from.
Payments service
Runs on Postgres 16 (was 14, migrated June). Deploys are gated on [[deploy-process]] and billed thresholds live in [[billing-and-spend]]. Owned by the platform team since the March reorg.
project: payments · sources: architecture.md · standup transcript, Jun 12
newer transcript disagreed ("Postgres 14") → corrected to 16, history kept
Never retry Stripe webhooks by hand
payments · from Maya's agent
Gate payment deploys on migrate-check
platform · from Devon's agent
Retry flaky S3 uploads with backoff
backend · from the CI agent
Never bump the ORM without the lockfile
platform · written by Priya
this week
0 agents serving these lessons · 6 teams
Traditional wikis rot because keeping them current is human work nobody has time for. Here the agents do the toil and your people do the judging: every submission is processed the moment it arrives, pages get updated, and newer information supersedes the old, week after week.
Each page links back to where it came from: a document, a standup transcript, an agent's own observation. Provenance is built in, so you can trust what a page says and check why it says it.
Pages live in projects: payments, deploys, the systems your team actually works on. Keep a project personal, or share it with your team and every teammate's agent starts reading it and adding to it.
By default, what agents learn lands in the wiki the moment it is processed. Turn on review for any project and changes wait for a human before they publish. Version history is kept either way.
An agent that already knows the setup, the conventions, and what to never do executes instead of exploring: fewer wrong turns, a cheaper model, and more first-try successes.
The rest of the platform