Luke F. Walton Research
Answerability and Authored AI Systems
Two papers. A reference implementation, set apart.
Papers on answerability, authorship, and machine-mediated action: one diagnoses the
failure in which no one authored the decision, the other shows its live market form on
the answer channel. The papers stand on their own; Answer Engine — technical note,
repository, and live site — is one runnable shape of the argument, offered separately
for engineers who want to read and run the contract in code.
DOI records prove the works.
ORCID proves the person.
lukefwalton.com explains the system.
Jump to section
- The papers
- Technical implementation
- Reading order
- Lexicon
- Citations
The papers
DOI records prove the works; site pages are the canonical surfaces here.
Preprint
Diagnoses the special failure: no one authored the decision.
Read when you are working on responsibility gaps, human oversight, meaningful human control, or the difference between control and authorship.
Page ·DOI ·PhilPapers ·CC BY-NC-ND 4.0
The Captured Oracle: Authorship and Agency in the Ethics of Answer-Engine Optimization
Preprint
Shows the live market form: the answer channel gets captured.
Read when you are working on answer engines, AEO, AI-mediated markets, retrieval, or covert authorship.
Page ·DOI ·PhilPapers ·CC BY-NC-ND 4.0
Technical implementation
Set apart from the papers: a technical note, an open-source repository, and a live deployment. Answer Engine is one runnable shape of the argument — not a philosophical work, but a reference implementation engineers can clone, run, and push against.
Technical implementation · technical note
States the design contract in prose — retrieval, citation, refusal, the no-leak boundary, and scaling notes from deployment.
Read when you want the runnable pattern explained as prose — retrieval, citation, refusal, the no-leak boundary, and how cost choices were gated at scale.
Page ·DOI ·GitHub ·CC BY-NC-ND 4.0
Technical implementation · software artifact
Clone-and-run repository — the runnable implementation the note describes.
Read when you want to clone, run, and read the implementation in code.
Page ·DOI ·GitHub ·Apache-2.0
Reading order
- Start with The Decision No One Authored for the core problem.
- Read The Captured Oracle for answer engines and AEO.
The papers move from diagnosis to the live market form.
For engineers
The papers stand on their own. If you build systems, here is one way to implement the philosophy — retrieval held outside the model, citations grounded, refusals tested.
- Read the technical note for the design contract — what may enter a prompt, what must stay out, and when to decline.
- Clone answer-engine, run the example corpus, and read the source in one sitting.
- Inspect Ask the Archive on this site for the live deployment behind the search.
Issues, PRs, and disagreement are welcome. This is a discussion, not a lecture — the repo is small on purpose so the contract stays readable; production lessons belong in the conversation too.
Lexicon
The Answerability Lexicon — defined terms used across the papers.
- Answerability
- the obligation of a person or institution to give reasons for a decision and stand behind its consequences. (Japanese: 答責性 / tōsekisei, as distinct from 説明責任 / explanation-responsibility.)
- Answerability gap
- when an automated system produces consequential outputs but no responsible actor can fully explain, own, or correct the decision.
- Captured oracle
- an answer system whose supposedly neutral outputs are shaped by hidden optimization, incentives, or control over the frame of retrieval.
- Decision laundering
- using automation to make a human or institutional choice appear neutral, inevitable, or machine-derived.
- Scapegoat layer
- the lowest-power human or team left to absorb blame for an automated decision they did not meaningfully author.
- Authored decision
- a decision whose responsible actor, evaluative frame, reasons, and consequences can be identified and answered for.
Citations
Pick a style and copy — APA, Chicago, BibTeX, RIS (for Zotero, EndNote, Mendeley),
or a compact prose line with DOI. Per-paper pages carry the same toggle under
Cite.
Technical implementation
Technical implementation · technical note
Technical implementation · software artifact