FDE Guide

Research and evidence

Research Ledger

Dated primary-source research, portable findings, attribution, uncertainty, and implementation implications behind The FDE Guide.

By David AhmannUpdated 2 min read

This folder holds dated evidence that supports the implementation library.

Repository source review: 2026-08-10. For the current dated ledger and solution evidence notes, source location, publication date, attribution, and evidence tier were rechecked. Link reachability and first-party publication do not establish general validity; every implementation pattern still requires local evaluation.

How sources are admitted

Core guidance requires one of:

  • Official protocol specifications, SDK release notes, security advisories, or engineering blogs
  • Reputable research with a reproducible artifact, clear methodology, or directly inspectable benchmark
  • First-party operating reports from identifiable practitioners when the post contains concrete implementation detail
  • Incident reports from the affected organization or a clearly labeled preliminary disclosure

Social, Reddit, YouTube, and news are research channels—not automatic authorities. A post or article enters core guidance only when it is either a qualified first-party field report or points to a primary technical artifact. Otherwise it is recorded as a lead or excluded.

Current research sets

  • Production-agent source ledger — vetted findings reviewed from 2026-02-07 through 2026-08-07, plus explicitly marked canonical sources published earlier and revalidated during that window; includes implementation patterns, anti-patterns, and source-quality notes.
  • AI Engineer production-agent video index — chapter-level practitioner talks with corroboration and claim limits.
  • Operational-redesign and applied-AI practice note — supplied practitioner material and one directly reviewed organizational-change framework, with portable lessons separated from attribution and forecast claims.
  • Evidence graphs and change intelligence — architecture/catalog/lineage sources and project implementation leads, scoped to derived maps and impact review rather than graph-driven authority.
  • Reference-solution standards note — primary identity, provisioning, usage-metering, and telemetry anchors for the enterprise-foundation and deployment accelerators, with provider and conformance limits.
  • Business-flow and vertical-solution evidence note — outcome-led solution design, operational applications, healthcare access workflows, financial-investigation evidence, and OT context boundaries used by the business-flow and industry profiles.
  • FDE commercial and professional-practice note — secondary-source leads for pilot graduation, continuation health, delivery-portfolio economics, responsible reuse, and professional boundaries; excludes copied content, commercial adaptation, benchmarks, and pricing doctrine.
  • FDE product-boundaries and capability-transfer note — directly inspectable practitioner evidence for contribution zones, product feedback, shadow-product avoidance, receiving-team capability, and reuse-rights decisions, with organizational claims kept non-normative.

Archive

Source fields

Each core-evidence entry records a stable ID, source date or review date, source type, practical finding, and portable pattern. Caveats are included when recency, methodology, attribution, maturity, or generalizability limits how the source should be used. Library pages cite entries by ID so a recommendation can be traced back to its evidence and re-evaluated as platforms change.