{
  "id": 3875799,
  "title": "Mind Discipline: Why Our AI Advisor Only Reads Hand-Crafted Contracts",
  "url": "https://urgent.news/2026/08/28/mind-discipline-why-our-ai-advisor-only-reads-hand-crafted-contracts",
  "topic": "ai",
  "section": "AI",
  "published": "2026-08-28T03:12:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/brettryan/mind-discipline-why-our-ai-advisor-only-reads-hand-crafted-contracts-4n5a"
  },
  "original_language": "en",
  "account": "In his second account, the author recounts a pivotal moment when their Confluence documentation was unexpectedly deleted, serving as a wake-up call about the importance of keeping documentation alongside code. This realization led to the adoption of a new architectural philosophy: treating documentation as a contract, stored in a unified, git-backed format. By doing so, the startup eliminated the need for a bloated, detached corporate wiki and created a zero-overhead, anti-AI AI strategy. This strategy utilizes GitLab CI/CD and Google Workspace to build a secure, managed Retrieval-Augmented Generation (RAG) pipeline. The central idea behind this approach is to prioritize human intent over AI generation, treating AI as a principal architect and advisor rather than a code generator. To achieve this, the team drafts several markdown files within the project repository: README.md, INTERFACE.md, and API.md. These documents serve as the source of truth, defining the component's internal mechanisms, public-facing boundaries, and exposed ReST endpoints. The author emphasizes that if a public endpoint or module contract isn't documented in the API.md file or the interface contracts aren't exposed in INTERFACE.md, then, to the rest of the system and the AI advisor, it does not exist. This approach ensures deep clarity of thought before code execution and promotes a more intentional, hand-crafted software development process.",
  "summary": "In my first post, I wrote about why I spent my first week writing zero business logic and instead built rig - our lightweight, POSIX-compliant local provisioning tool. It was my way of rejecting \"wiki-ops\" and applying Infrastructure-as-Code (IaC) discipline to our local environments so that a hardware failure means minutes of downtime, not a week. But as I transitioned into Week Two, I was hit…",
  "key_points": [
    "Startup treats documentation as contracts in git-backed format",
    "AI advisor only reads hand-crafted markdown files (README, INTERFACE, API)",
    "Contracts define internal mechanisms, public boundaries, ReST endpoints"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}