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 is the founder and maintainer of AsDecided. He builds tools for making agent-assisted software development more deterministic, inspectable and useful. Core, the public specification, release history and product limits are developed in the open so readers can inspect the source behind each claim.
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.
- Product overview ↗Canonical explanation of the system.
- Specification ↗Language-neutral contract for decision artifacts.
- Core source ↗CLI and read-only MCP implementation.
- Changelog ↗Versioned release evidence.
- Canonical source map ↗Claim-by-claim authority and citation guidance.
EDITORIAL METHODOLOGY
Evidence before opinion.
Product claims are checked against the public specification, current documentation, source and release record. External technical claims prefer primary documentation or the original research. Commands and implementation examples are checked against the published product surface before they appear in a guide.
Editorial pages may be drafted with AI assistance, but Tom reviews the published argument, evidence, examples and links as the named author-maintainer. A page’s updated date changes only when its substance changes. Corrections retain the canonical URL and are reviewed against the source that governs the claim.
- 01 Identify the narrowest authoritative source.
- 02 Separate released fact from editorial interpretation.
- 03 Check commands, examples, scope and limitations.
- 04 Publish named authorship, dates and correction routes.
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.