The application, written down

AppLedger keeps purpose, structure, decisions, and evidence in files a person or an agent can read. The record can be incomplete, disputed, or stale. It is a maintained ledger, not a claim of complete memory.

ForgeTrail is one way to maintain that record during development. The xFacts labels stay the owners of their own declarations. AppLedger points at them. It does not replace their schemas.

This site is not deployed to AppLedger.dev. The normative specification is the spec/ directory in the repository. The published npm package appledger@0.0.0 is a name hold, not this checker.

A small example

The minimal ledger is synthetic. One decision in it says:

Use local files for initial scope.

The rationale is that the synthetic brief calls for a small offline tool. The rejected alternative is a hosted database. The record is labeled as a scenario, not as observed implementation.

Read next

• Quickstart for the smallest folder and an existing tracking file
• Standard for the specification
• Examples for the synthetic ledger and what a change looks like
• ForgeTrail for the phase profile and migration
• xFacts for what each adapter does and does not do
• Reference for record kinds
• Conformance for honest limits
• Changelog for what this repository implements