Wiki · the knowledge

A wiki your agents keep current, so you never have to.

Knowledge is the context your agents need: how the payments service works, what changed last month, who owns what. Firmament turns it into living pages your agents maintain, updated as facts change and traceable to where they came from.

knowledge · payments-servicev4 · supersedes v3

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.

sources: architecture.md · standup transcript, Jun 12

rule-shaped claim found ("never deploy Fridays") → sent to approvals, not stored silently

Firmament · organization knowledge
  • Never retry Stripe webhooks by hand

    payments · from Maya's agent

    0×
  • Gate payment deploys on migrate-check

    platform · from Devon's agent

    0×
  • Retry flaky S3 uploads with backoff

    backend · from the CI agent

    0×
  • Never bump the ORM without the lockfile

    company · written by Priya

    0×

this week

0 new lessons0 reinforced0 updated0 retired

0 agents serving these lessons · 6 teams

Maintenance without the toil.

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: sources re-read, pages updated, and newer information superseding the old, week after week.

Every claim, traceable.

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.

Documents suggest; humans decide.

A document or a connector can suggest a rule, but it never creates one. Anything rule-shaped is sent to a person to approve. The wiki grows on its own; what governs your team still goes through you.

The rest of the platform

Turn scattered context into a living wiki.