ABOUT / ASDECIDED

Decisions are easier to trust when their source is visible.

AsDecided is an open-source, repository-native system for recording, retrieving, citing and enforcing the engineering decisions that sit behind AI-assisted software development.

THE MAINTAINER

Built in public by Tom Ballard.

Tom builds tools for making agent-assisted software development more deterministic, inspectable and useful. AsDecided is developed in the open so its specification, source, releases and limits can be checked by the people who rely on it.

EDITORIAL AND CORRECTIONS

What the public record means.

Product documentation and the specification are the canonical sources for AsDecided behaviour. Changelog pages record released capabilities. Notes explain engineering patterns and comparisons; they are not a substitute for a product guarantee or a published benchmark.

Claims are written with their scope and evidence visible. If a note, link or product description is inaccurate, report the exact page and correction through the public GitHub organisation. The correction is reviewed against the source or release record, then the page’s update date is changed when the content changes.

OFFICIAL SOURCES

Follow the authority, not the paraphrase.

SECURITY BOUNDARIES

Keep the source inspectable.

AsDecided does not need repository write access to retrieve a decision. Core and the public MCP surface are read-only by design; enforcement runs in the repository’s own checks. Report a security concern through the public GitHub organisation so it can be tracked against the source and release record.

CONTACT AND CORRECTIONS

Point to the exact record.

For a correction, citation question or product issue, link to the exact AsDecided page or repository artifact and open an issue in the public GitHub organisation. The maintainer reviews changes against the canonical documentation or specification.

PRIVACY NOTES

No editorial claim is hidden.

This public site does not intentionally add advertising trackers or collect form submissions. Hosting, CDN and linked services may process ordinary request metadata under their own policies; use the linked canonical documentation and source when evaluating product or data-handling claims.