{
  "aliases": {},
  "anchor_aliases": {},
  "build_id": "943fab7405f66fa3",
  "entities": {
    "availability:current": {
      "as_of": "2026-09-25",
      "data": {
        "level": "limited",
        "location": "Turin, Italy",
        "open_to": [
          "role",
          "project",
          "advice",
          "collaboration"
        ],
        "remote": true,
        "short": "Building Radicas · open to conversations",
        "timezone": "CET"
      },
      "slug": "current",
      "stale_after": "2026-10-25",
      "status": "published",
      "summary": "Building Radicas. Open to conversations about agentic AI, developer tooling and open-source infrastructure.",
      "type": "availability",
      "withheld": []
    },
    "experience:founder-in-residence-reef": {
      "data": {
        "employer": "org:reef-by-vento",
        "end": "2026-07",
        "highlights": [
          {
            "id": "highlight-selection",
            "text": "Selected for the five-month full-time programme at OGR Torino, one of forty participants from several hundred applicants."
          },
          {
            "id": "highlight-zero-to-users",
            "text": "Took the product from zero to first users — problem discovery, architecture, implementation and go-to-market."
          }
        ],
        "location": "Turin",
        "role_name": "Founder in Residence",
        "skills": [
          {
            "id": "skill:product-discovery",
            "note": "problem discovery through to go-to-market"
          }
        ],
        "sources": [
          "source:linkedin-profile"
        ],
        "start": "2026-02"
      },
      "description": "Founder in Residence at Reef by Vento, the venture-building programme run by Exor's early-stage VC arm.",
      "lead": {
        "markdown": "The programme Radicas was built inside.",
        "text": "The programme Radicas was built inside."
      },
      "slug": "founder-in-residence-reef",
      "status": "published",
      "summary": "Five-month full-time venture-building programme run by Vento, Exor's early-stage VC arm, where Radicas went from problem to first users.",
      "title": "Founder in Residence, Reef by Vento",
      "type": "experience",
      "withheld": []
    },
    "experience:founder-radicas": {
      "as_of": "2026-09-19",
      "data": {
        "employer": "org:radicas",
        "highlights": [
          {
            "id": "highlight-cost-attribution",
            "text": "Cost attribution and spend observability across multiple LLM providers, broken down per feature and per tenant, with budget alerting and anomaly detection."
          },
          {
            "id": "highlight-model-routing",
            "text": "A routing layer that picks the model tier per request from task complexity, latency budget and cost ceiling."
          },
          {
            "id": "highlight-eval-gate",
            "text": "Built the product's own AI layer with an eval harness gating every release and quality metrics tracked per commit."
          }
        ],
        "location": "Turin, remote",
        "role_name": "Founder and engineer",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "the delivery approach behind the product"
          },
          {
            "id": "skill:finops-for-ai",
            "note": "the product itself"
          },
          {
            "id": "skill:llm-observability",
            "note": "OpenTelemetry gen_ai spans priced and reconciled"
          },
          {
            "id": "skill:model-routing",
            "note": "model tier selected per request against a cost ceiling"
          },
          {
            "id": "skill:eval-harnesses",
            "note": "an eval harness gates every release"
          },
          {
            "id": "skill:python-fastapi"
          },
          {
            "id": "skill:multi-tenant-saas"
          }
        ],
        "sources": [
          "source:radicas-site"
        ],
        "start": "2026-02"
      },
      "description": "Founder and engineer at Radicas, a FinOps platform for AI workloads.",
      "lead": {
        "markdown": "See the [Radicas case study](../projects/radicas/index.md) for the architecture and the decisions behind it.",
        "text": "See the Radicas case study for the architecture and the decisions behind it."
      },
      "slug": "founder-radicas",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "Building a FinOps platform for AI workloads — cost attribution, model routing and spend observability across LLM providers.",
      "title": "Founder and engineer, Radicas",
      "type": "experience",
      "withheld": []
    },
    "experience:salento-racing-team": {
      "data": {
        "employer": "org:salento-racing",
        "end": "2017-08",
        "highlights": [
          {
            "id": "highlight-formula-sae",
            "text": "Built and maintained the electrical system of a Formula SAE car alongside the engineering degree."
          }
        ],
        "location": "Lecce",
        "role_name": "Electrical division",
        "skills": [
          {
            "id": "skill:embedded-electronics",
            "note": "the car's electrical system"
          }
        ],
        "start": "2016-09"
      },
      "description": "Electrical division member of Salento Racing Team, the University of Salento Formula SAE team.",
      "lead": {
        "markdown": "University team, kept here because it is where the hands-on engineering started.",
        "text": "University team, kept here because it is where the hands-on engineering started."
      },
      "slug": "salento-racing-team",
      "status": "published",
      "summary": "Electrical division of the University of Salento's Formula SAE team, during the engineering degree.",
      "title": "Electrical division, Salento Racing Team",
      "type": "experience",
      "withheld": []
    },
    "experience:senior-swe-fincons-itv": {
      "data": {
        "client": "org:itv",
        "employer": "org:fincons-group",
        "end": "2026-02",
        "highlights": [
          {
            "id": "highlight-integration-boundaries",
            "text": "Architected and evolved Python services around SDVI Rally, defining integration boundaries and data contracts across ingest and orchestration flows."
          },
          {
            "id": "highlight-supply-chain-automation",
            "text": "Automated media supply-chain operations with AWS Lambda and DynamoDB on Terraform-backed CI/CD, with standardised observability and runbooks."
          }
        ],
        "location": "London, remote",
        "role_name": "Senior Software Engineer",
        "skills": [
          {
            "id": "skill:python-fastapi",
            "note": "the services around the media orchestration platform"
          },
          {
            "id": "skill:aws-serverless",
            "note": "Lambda and DynamoDB automation"
          },
          {
            "id": "skill:terraform",
            "note": "Terraform-backed CI/CD"
          },
          {
            "id": "skill:architecture-decision-records",
            "note": "decisions formalised as ADRs and design docs"
          }
        ],
        "sources": [
          "source:linkedin-profile"
        ],
        "start": "2025-07"
      },
      "description": "Senior Software Engineer at Fincons Group, working on media supply-chain automation for ITV.",
      "lead": {
        "markdown": "Consulting engagement through Fincons Group, working on the media supply chain of a national broadcaster.",
        "text": "Consulting engagement through Fincons Group, working on the media supply chain of a national broadcaster."
      },
      "slug": "senior-swe-fincons-itv",
      "status": "published",
      "summary": "Python services and media supply-chain automation for ITV, delivered as a consultant through Fincons Group.",
      "title": "Senior Software Engineer, Fincons Group",
      "type": "experience",
      "withheld": []
    },
    "experience:swe-exprivia-enel": {
      "data": {
        "client": "org:enel-green-power",
        "employer": "org:exprivia",
        "end": "2021-04",
        "highlights": [
          {
            "id": "highlight-energy-systems",
            "text": "Delivered Conceptual Design 2.0 for solar PV design, SDEE for dam data exchange, and EnelCheck 2.0 for plant safety auditing."
          },
          {
            "id": "highlight-backend-algorithms",
            "text": "Built algorithms and backend services on AWS serverless and Docker/Kubernetes, integrated with OpenText AppWorks."
          }
        ],
        "location": "Lecce",
        "role_name": "Software Engineer",
        "skills": [
          {
            "id": "skill:python-fastapi",
            "note": "Python 3 backend services"
          },
          {
            "id": "skill:java-spring",
            "note": "Java 11, J2EE, Hibernate and JPA"
          },
          {
            "id": "skill:aws-serverless"
          },
          {
            "id": "skill:kubernetes"
          }
        ],
        "sources": [
          "source:linkedin-profile"
        ],
        "start": "2018-05"
      },
      "description": "Software Engineer at Exprivia, delivering backend systems for Enel Green Power.",
      "lead": {
        "markdown": "First engineering role, across three systems in the energy sector.",
        "text": "First engineering role, across three systems in the energy sector."
      },
      "slug": "swe-exprivia-enel",
      "status": "published",
      "summary": "Backend services and algorithms for Enel Green Power — solar PV design, dam data exchange and plant safety auditing on AWS serverless and Kubernetes.",
      "title": "Software Engineer, Exprivia",
      "type": "experience",
      "withheld": []
    },
    "offering:ai-cost-audit": {
      "as_of": "2026-09-25",
      "data": {
        "deliverable": "An analysis report, and the quick wins that can ship straight away.",
        "duration": "About one week.",
        "pricing": "fixed price",
        "scope": "Cost attribution per feature and per tenant; recurring waste such as oversized prompts, the wrong model tier for the task, uncontrolled retries and missing caching; a reduction plan with estimated savings and prioritised actions."
      },
      "slug": "ai-cost-audit",
      "stale_after": "2026-12-24",
      "status": "published",
      "summary": "A review of what an LLM system already in production costs, and where the spend goes.",
      "title": "AI cost audit",
      "type": "offering",
      "withheld": []
    },
    "offering:ai-reliability-retainer": {
      "as_of": "2026-09-25",
      "data": {
        "pricing": "monthly commitment",
        "scope": "Eval monitoring, cost control, model upgrades and incident response."
      },
      "slug": "ai-reliability-retainer",
      "stale_after": "2026-12-24",
      "status": "published",
      "summary": "Ongoing care for AI systems already in production.",
      "title": "AI reliability retainer",
      "type": "offering",
      "withheld": []
    },
    "offering:ai-system-design-and-build": {
      "as_of": "2026-09-25",
      "data": {
        "deliverable": "A working system with tests, documentation and runbooks.",
        "duration": "Three to four weeks per use case.",
        "scope": "Ingestion and retrieval pipelines, agent orchestration, AI automation, an eval harness, observability and cloud deployment."
      },
      "slug": "ai-system-design-and-build",
      "stale_after": "2026-12-24",
      "status": "published",
      "summary": "One use case taken from design to production.",
      "title": "AI system design and build",
      "type": "offering",
      "withheld": []
    },
    "org:enel-green-power": {
      "data": {
        "name": "Enel Green Power",
        "sector": "Energy",
        "url": "https://www.enelgreenpower.com"
      },
      "slug": "enel-green-power",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:exprivia": {
      "data": {
        "name": "Exprivia",
        "url": "https://www.exprivia.it"
      },
      "slug": "exprivia",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:fincons-group": {
      "data": {
        "name": "Fincons Group",
        "url": "https://www.finconsgroup.com"
      },
      "slug": "fincons-group",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:itv": {
      "data": {
        "name": "ITV",
        "sector": "Media and broadcasting",
        "url": "https://www.itv.com"
      },
      "slug": "itv",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:niksen": {
      "data": {
        "name": "The Niksen Company"
      },
      "slug": "niksen",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:radicas": {
      "data": {
        "name": "Radicas",
        "sector": "AI infrastructure",
        "url": "https://www.radicas.ai"
      },
      "slug": "radicas",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:reef-by-vento": {
      "data": {
        "name": "Reef by Vento",
        "note": "Early-stage venture-building programme run by Vento, Exor's early-stage VC arm.",
        "url": "https://vento.vc"
      },
      "slug": "reef-by-vento",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "org:salento-racing": {
      "data": {
        "name": "Salento Racing Team",
        "note": "University Formula SAE team, University of Salento."
      },
      "slug": "salento-racing",
      "status": "published",
      "type": "org",
      "withheld": []
    },
    "page:about": {
      "data": {},
      "description": "Who Francesco Fiore is, what he works on, how he works, and the background behind it.",
      "lead": {
        "markdown": "Francesco is a software engineer based in Turin. He founded Radicas, a FinOps platform for AI workloads, and maintains open-source tools for agents that do real engineering work.",
        "text": "Francesco is a software engineer based in Turin. He founded Radicas, a FinOps platform for AI workloads, and maintains open-source tools for agents that do real engineering work."
      },
      "slug": "about",
      "status": "published",
      "summary": "Francesco Fiore is a software engineer based in Turin, working on agentic AI systems after backend and cloud work in the energy and media sectors since 2018.",
      "title": "About Francesco Fiore",
      "type": "page",
      "withheld": []
    },
    "page:home": {
      "data": {
        "suggested_paths": [
          {
            "target": "project:radicas#problem",
            "text": "How the cost of an AI feature is attributed"
          },
          {
            "target": "principle:let-the-system-do-the-heavy-lifting#what-the-structure-actually-is",
            "text": "What delivery through coding agents looks like"
          },
          {
            "target": "project:accreta#decision-compile-not-retrieve",
            "text": "Why a knowledge base should be compiled, not retrieved from"
          },
          {
            "target": "project:praxis#decision-guardrails-in-kernel",
            "text": "Guardrails in an agent runtime's kernel"
          }
        ]
      },
      "description": "Francesco Fiore builds agentic AI systems and the infrastructure that keeps them measurable. Projects, decisions and results, with sources.",
      "lead": {
        "markdown": "Francesco builds agentic AI systems and the parts that decide whether they can run in production: what each feature costs, whether a release still passes its evals, and what the agent is allowed to do. Since 2018 that has meant backend systems for energy and media companies; since 2026, Radicas and open-source tooling for coding agents.",
        "text": "Francesco builds agentic AI systems and the parts that decide whether they can run in production: what each feature costs, whether a release still passes its evals, and what the agent is allowed to do. Since 2018 that has meant backend systems for energy and media companies; since 2026, Radicas and open-source tooling for coding agents."
      },
      "slug": "home",
      "status": "published",
      "summary": "Francesco Fiore is a software engineer who builds agentic AI systems and the parts that make them safe to run — cost attribution, evaluation, observability and guardrails.",
      "title": "Francesco Fiore",
      "type": "page",
      "withheld": []
    },
    "page:privacy": {
      "data": {
        "derived_from": [
          "docs/decisions/ADR-0019-accessibility-performance-budgets.md",
          "docs/decisions/ADR-0036-client-storage-context-payload.md",
          "docs/decisions/ADR-0043-provider-interface-model-tiers.md",
          "docs/decisions/ADR-0053-consent-tier-matrix.md",
          "docs/decisions/ADR-0054-retention-redaction-schedule.md",
          "docs/decisions/ADR-0056-turn-trace-schema.md",
          "docs/decisions/ADR-0063-one-contact-backend-no-js-review.md",
          "docs/decisions/ADR-0064-contact-fields-and-when-offered.md",
          "docs/decisions/ADR-0066-delivery-owner-mailbox-transport.md",
          "docs/decisions/ADR-0067-contact-row-qualified-lead-origin.md",
          "docs/decisions/ADR-0069-one-worker-site-origin.md",
          "docs/decisions/ADR-0070-ledger-memory-trace-stores.md",
          "docs/decisions/ADR-0071-ask-without-a-query-string.md",
          "docs/decisions/ADR-0073-residency-processors-cost.md",
          "docs/decisions/ADR-0074-mail-transport-cloudflare-send-email.md",
          "docs/decisions/ADR-0081-scope-gate-on-jev.md",
          "docs/decisions/ADR-0082-jev-slots-and-processor-route.md",
          "docs/decisions/ADR-0083-privacy-notice-in-house.md",
          "docs/decisions/ADR-0084-keeping-disclosures-true.md",
          "docs/decisions/ADR-0085-edge-adds-nothing.md",
          "docs/decisions/ADR-0086-page-views-from-zone-analytics.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "The privacy notice of francescofiore.dev. No cookies, no stored text from visitors, and every processor named with what it receives and keeps.",
      "lead": {
        "markdown": "**In short.** This site sets no cookies. On your device it keeps nothing, except your conversation with the assistant, for as long as that tab is open. Nothing you type is stored by this site. What you ask the assistant is sent to two companies so that it can be answered. A message you send me goes to my mailbox. The rest of this page says exactly what goes where, and for how long.",
        "text": "In short. This site sets no cookies. On your device it keeps nothing, except your conversation with the assistant, for as long as that tab is open. Nothing you type is stored by this site. What you ask the assistant is sent to two companies so that it can be answered. A message you send me goes to my mailbox. The rest of this page says exactly what goes where, and for how long."
      },
      "slug": "privacy",
      "status": "published",
      "summary": "What this site does with your data, by whom, where, for how long, on what basis, and how to exercise your rights.",
      "title": "Privacy",
      "type": "page",
      "withheld": []
    },
    "page:work-with-me": {
      "data": {},
      "description": "Working with Francesco Fiore on agentic AI, LLM cost and reliability, and backend architecture. Current availability and how to get in touch.",
      "lead": {
        "markdown": "The work that fits best is where an AI feature has to become a system someone can run, pay for and trust: attributing its cost, routing between models, gating releases on evals, tracing it end to end, and writing down the architecture decisions behind it. The backend and cloud work before that — energy platforms, a broadcaster's media supply chain, AWS and Kubernetes — is under [experience](/experience).",
        "text": "The work that fits best is where an AI feature has to become a system someone can run, pay for and trust: attributing its cost, routing between models, gating releases on evals, tracing it end to end, and writing down the architecture decisions behind it. The backend and cloud work before that — energy platforms, a broadcaster's media supply chain, AWS and Kubernetes — is under experience."
      },
      "slug": "work-with-me",
      "status": "published",
      "summary": "How to work with Francesco Fiore — a role, a project, advice or a collaboration on agentic AI, LLM cost and reliability, or backend and cloud architecture.",
      "title": "Work with Francesco",
      "type": "page",
      "withheld": []
    },
    "person:francesco-fiore": {
      "as_of": "2026-09-25",
      "data": {
        "credentials": [
          {
            "date": "2025-04",
            "issuer": "MongoDB University",
            "name": "MongoDB SI Architect",
            "note": "Includes Atlas Vector Search for RAG workloads."
          },
          {
            "date": "2023-05",
            "issuer": "Amazon Web Services",
            "name": "AWS Certified Developer – Associate"
          },
          {
            "date": "2022-07",
            "issuer": "MongoDB University",
            "name": "MongoDB Certified Developer Associate"
          }
        ],
        "education": [
          {
            "degree": "B.Sc. in Information Engineering",
            "end": 2018,
            "institution": "University of Salento",
            "location": "Lecce",
            "start": 2014
          }
        ],
        "headline": "Senior Software Engineer and CTO",
        "languages": [
          {
            "level": "native",
            "name": "Italian"
          },
          {
            "level": "C1",
            "name": "English"
          }
        ],
        "location": "Turin, Italy",
        "name": "Francesco Fiore",
        "portrait": {
          "alt": "Francesco Fiore",
          "src": "assets/b3ac7c614a01.png"
        },
        "sources": [
          "source:github-profile",
          "source:linkedin-profile"
        ],
        "url": "https://francescofiore.dev"
      },
      "description": "Francesco Fiore, software engineer and founder of Radicas. Agentic AI, LLM cost and observability, and the architecture decisions behind them.",
      "slug": "francesco-fiore",
      "stale_after": "2027-03-24",
      "status": "published",
      "summary": "Software engineer building agentic AI systems and the infrastructure that makes them measurable — cost attribution, evaluation, observability and guardrails.",
      "title": "Francesco Fiore",
      "type": "person",
      "withheld": []
    },
    "principle:let-the-system-do-the-heavy-lifting": {
      "data": {
        "examples": [
          "project:accreta#decision-compile-not-retrieve",
          "project:accreta#decision-mcp-beside-cli",
          "project:coding-agent-sync",
          "project:accreta-atlas",
          "project:claude-account-switcher#claim-built-in-a-day"
        ],
        "skills": [
          {
            "id": "skill:agent-assisted-delivery"
          },
          {
            "id": "skill:context-engineering"
          }
        ],
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "The working principle behind most of the recent work — complex systems delivered fast through structured AI coding agents.",
      "lead": {
        "markdown": "Most of the work now runs through coding agents. That changes what the engineering job is: less typing, far more deciding what is true, writing it down where an agent will read it, and building the guardrails that make an agent's output reviewable.\n\nThe speed is a consequence, not the goal. A system gets built quickly because the agent is not rediscovering the codebase on every session — the architecture, the contracts and the invariants are already written down, the decisions already have their reasoning attached, and the tests and CI say plainly when something has broken. Take that structure away and the same agent produces work that has to be redone.",
        "text": "Most of the work now runs through coding agents. That changes what the engineering job is: less typing, far more deciding what is true, writing it down where an agent will read it, and building the guardrails that make an agent's output reviewable.\n\nThe speed is a consequence, not the goal. A system gets built quickly because the agent is not rediscovering the codebase on every session — the architecture, the contracts and the invariants are already written down, the decisions already have their reasoning attached, and the tests and CI say plainly when something has broken. Take that structure away and the same agent produces work that has to be redone."
      },
      "slug": "let-the-system-do-the-heavy-lifting",
      "status": "published",
      "summary": "A good engineer removes repetitive work and lets the system carry it. Applied to delivery itself, that means designing, building, testing and shipping through coding agents that have been given the structure to work reliably.",
      "title": "Let the system do the heavy lifting",
      "type": "principle",
      "withheld": []
    },
    "processing:privacy": {
      "as_of": "2026-10-20",
      "data": {
        "controller": {
          "contact": "hello@francescofiore.dev",
          "country": "Italy",
          "name": "Francesco Fiore",
          "phase": 1,
          "source": [
            "ADR-0074",
            "ADR-0083"
          ]
        },
        "derived_from": [
          "docs/decisions/ADR-0036-client-storage-context-payload.md",
          "docs/decisions/ADR-0043-provider-interface-model-tiers.md",
          "docs/decisions/ADR-0045-consented-identifier-memory-store.md",
          "docs/decisions/ADR-0046-memory-record-interest-vocabulary.md",
          "docs/decisions/ADR-0052-abuse-bots-alerts.md",
          "docs/decisions/ADR-0053-consent-tier-matrix.md",
          "docs/decisions/ADR-0054-retention-redaction-schedule.md",
          "docs/decisions/ADR-0056-turn-trace-schema.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md",
          "docs/decisions/ADR-0063-one-contact-backend-no-js-review.md",
          "docs/decisions/ADR-0066-delivery-owner-mailbox-transport.md",
          "docs/decisions/ADR-0067-contact-row-qualified-lead-origin.md",
          "docs/decisions/ADR-0070-ledger-memory-trace-stores.md",
          "docs/decisions/ADR-0071-ask-without-a-query-string.md",
          "docs/decisions/ADR-0073-residency-processors-cost.md",
          "docs/decisions/ADR-0074-mail-transport-cloudflare-send-email.md",
          "docs/decisions/ADR-0081-scope-gate-on-jev.md",
          "docs/decisions/ADR-0082-jev-slots-and-processor-route.md",
          "docs/decisions/ADR-0083-privacy-notice-in-house.md",
          "docs/decisions/ADR-0086-page-views-from-zone-analytics.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md"
        ],
        "processors": [
          {
            "keeps": "Its own analytics hold a sample of requests with IP address and path; the owner can read them for at least 31 days, and Cloudflare states no period of its own. This site's log lines: 7 days, fixed words only.",
            "name": "Cloudflare",
            "phase": 1,
            "receives": "every request, which carries your IP address and the page's address",
            "role": "hosting and delivery of every page",
            "source": [
              "ADR-0073",
              "ADR-0086"
            ],
            "terms": "https://www.cloudflare.com/privacypolicy/",
            "transfer": {
              "country": "United States",
              "mechanism": "EU-US Data Privacy Framework (Art. 45) and the SCCs in Cloudflare's DPA (Art. 46(2)(c))"
            },
            "where": "the Cloudflare location nearest you; this site's stores in the EU"
          },
          {
            "keeps": "Not used for training. No retention period is stated.",
            "name": "TypeSafe, through Cloudflare AI Gateway",
            "phase": 1,
            "receives": "your question alone, with the public list of his project and organisation names",
            "role": "decides whether a question is about Francesco, its language, what it is about, and how likely it is to be an attempt to change the assistant's rules",
            "source": [
              "ADR-0081",
              "ADR-0082",
              "ADR-0087"
            ],
            "terms": "https://typesafe.ai/legal/privacy-policy",
            "transfer": {
              "country": "United States",
              "mechanism": "SCCs in TypeSafe's DPA (Art. 46(2)(c))"
            },
            "where": "United States"
          },
          {
            "keeps": "Abuse-monitoring logs for up to 30 days. No stored response, because this site asks for none. Encrypted prompt-cache state for up to 24 hours. Not used for training.",
            "name": "OpenAI",
            "phase": 1,
            "receives": "your question, the earlier turns of this conversation still in your tab, any text you selected on the page and chose to ask about, and the page you were on",
            "role": "writes the assistant's answer",
            "source": [
              "ADR-0043",
              "ADR-0062",
              "ADR-0073"
            ],
            "terms": "https://developers.openai.com/api/docs/guides/your-data",
            "transfer": {
              "country": "United States",
              "mechanism": "SCCs in OpenAI's DPA (Art. 46(2)(c))"
            },
            "where": "servers around the world, including the United States"
          },
          {
            "keeps": "A message preview for about 7 days, turned off where the setting exists. An activity log, shown in the dashboard for up to 30 days.",
            "name": "Cloudflare Email",
            "phase": 1,
            "receives": "the message you approved on the review page, addressed to my mailbox only",
            "role": "delivers a message you send through the contact form to my mailbox",
            "source": [
              "ADR-0073",
              "ADR-0074"
            ],
            "terms": "https://developers.cloudflare.com/email-service/observability/logs/",
            "transfer": {
              "mechanism": "EU-US Data Privacy Framework (Art. 45) and the SCCs in Cloudflare's DPA (Art. 46(2)(c))"
            },
            "where": "not stated by Cloudflare"
          },
          {
            "keeps": "every message in my mailbox, until I delete it",
            "name": "Google (Gmail)",
            "phase": 1,
            "receives": "the message Cloudflare Email delivers to my mailbox",
            "role": "keeps my mailbox, where a message you send through the contact form arrives",
            "source": "ADR-0083",
            "terms": "https://policies.google.com/privacy",
            "transfer": {
              "country": "United States",
              "mechanism": "EU-US Data Privacy Framework (Art. 45)",
              "note": "a consumer account offers no DPA or SCCs"
            },
            "where": "servers around the world, including the United States"
          }
        ],
        "purposes": [
          {
            "basis": "Art. 6(1)(f)",
            "data": "IP address, the page's address, what the browser sends with every request; totals per route and day, with no IP address",
            "interest": "to deliver and protect the site, and to know which pages are read",
            "key": "deliver-and-protect",
            "phase": 1,
            "processing": "delivering and securing pages; logs at the edge; the daily count of page requests",
            "retention": "see surfaces 2 and 7",
            "source": [
              "ADR-0083",
              "ADR-0086"
            ],
            "surfaces": [
              2,
              7
            ]
          },
          {
            "basis": "Art. 6(1)(f)",
            "data": "the question and what goes with it, as each provider receives it; the record per question; a scrambled IP address",
            "interest": "to answer the question you asked, and to keep the assistant working, within its budget and safe",
            "key": "answer-a-question",
            "phase": 1,
            "processing": "answering a question you ask the assistant; the record per question; the per-address counts that stop abuse",
            "retention": "see surfaces 1, 3, 4 and 7; the per-address counts are held in memory and gone within a day",
            "source": [
              "ADR-0052",
              "ADR-0070",
              "ADR-0082",
              "ADR-0083",
              "ADR-0087"
            ],
            "surfaces": [
              1,
              3,
              4,
              7
            ]
          },
          {
            "basis": "Art. 6(1)(b), steps taken at your request before a contract",
            "data": "your address, your message, and optionally your name and what you need",
            "key": "contact-about-work",
            "phase": 1,
            "processing": "a message you send about working together",
            "retention": "see surfaces 7, 8 and 9",
            "source": [
              "ADR-0063",
              "ADR-0083"
            ],
            "surfaces": [
              7,
              8,
              9
            ]
          },
          {
            "basis": "Art. 6(1)(f)",
            "data": "your address, your message, and optionally your name and what you need",
            "interest": "to read and reply to what you sent",
            "key": "contact-other",
            "phase": 1,
            "processing": "any other message you send",
            "retention": "see surfaces 7, 8 and 9",
            "source": [
              "ADR-0063",
              "ADR-0083"
            ],
            "surfaces": [
              7,
              8,
              9
            ]
          },
          {
            "basis": "Art. 6(1)(a) consent, and ePrivacy Art. 5(3) consent",
            "key": "analytics",
            "phase": 2,
            "processing": "analytics, if you turn it on, including the role your question states, such as recruiter or founder, if it states one",
            "source": [
              "ADR-0053",
              "ADR-0083",
              "ADR-0087"
            ],
            "surfaces": [
              5,
              7
            ]
          },
          {
            "basis": "Art. 6(1)(a) consent, and ePrivacy Art. 5(3) consent for the stored id",
            "data": "the random id and the memory record",
            "key": "memory",
            "phase": 3,
            "processing": "remembering you across visits, if you turn memory on",
            "retention": "180 days since your last visit, sliding",
            "source": [
              "ADR-0045",
              "ADR-0053",
              "ADR-0083"
            ],
            "surfaces": [
              5,
              6
            ]
          }
        ],
        "storage": [
          {
            "holds": "your conversation in this tab and a random id for it",
            "key": "ap.v1",
            "lifetime": "until you close the tab",
            "mechanism": "sessionStorage",
            "phase": 1,
            "source": "ADR-0036",
            "where": "/ask"
          },
          {
            "holds": "your two privacy choices, and a random id if you turned memory on",
            "key": "ap.mem.v1",
            "lifetime": "until you change or delete it",
            "mechanism": "localStorage",
            "phase": 2,
            "source": "ADR-0053",
            "where": "every page"
          }
        ],
        "surfaces": [
          {
            "control": "yours; clear your history",
            "holds": "a question typed into the ask box on a content page, carried to /ask after the \"#\" of the address and never sent to a server",
            "n": 1,
            "name": "Your browser history",
            "phase": 1,
            "retention": "as long as your browser keeps its history",
            "source": [
              "ADR-0054",
              "ADR-0071"
            ],
            "tier": "necessary",
            "where": "your browser"
          },
          {
            "control": "none",
            "holds": "this site's own log lines, in fixed words only; Cloudflare's sampled request analytics, with IP address and path",
            "n": 2,
            "name": "Logs at the edge",
            "phase": 1,
            "retention": "this site's log lines: 7 days; Cloudflare's analytics: readable by me for at least 31 days, with no period stated by Cloudflare",
            "source": [
              "ADR-0054",
              "ADR-0070",
              "ADR-0073",
              "ADR-0086"
            ],
            "tier": "necessary",
            "where": "Cloudflare"
          },
          {
            "control": "close the tab",
            "holds": "your conversation in this tab and a random id for it",
            "n": 3,
            "name": "Session storage, ap.v1",
            "phase": 1,
            "retention": "until you close the tab",
            "source": [
              "ADR-0036",
              "ADR-0054"
            ],
            "tier": "necessary",
            "where": "your browser"
          },
          {
            "control": "none; this page is the disclosure",
            "holds": "what each receives when you ask the assistant, listed above",
            "n": 4,
            "name": "The assistant's providers",
            "phase": 1,
            "retention": "each provider's own terms, as listed above",
            "source": [
              "ADR-0054",
              "ADR-0073",
              "ADR-0082"
            ],
            "tier": "necessary",
            "where": "TypeSafe, United States; OpenAI, servers around the world, including the United States"
          },
          {
            "control": "the delete control",
            "holds": "your two privacy choices, and a random id if you turned memory on",
            "n": 5,
            "name": "Local storage, ap.mem.v1",
            "phase": 2,
            "retention": "until you change or delete it",
            "source": [
              "ADR-0053",
              "ADR-0054"
            ],
            "tier": "personalisation",
            "where": "your browser"
          },
          {
            "control": "view, reset or delete it, at once and in full",
            "holds": "six fields of ids and fixed values under the random id, with no field that could hold text",
            "n": 6,
            "name": "The memory record",
            "phase": 3,
            "retention": "180 days since your last visit, sliding, then deleted",
            "source": [
              "ADR-0045",
              "ADR-0046",
              "ADR-0054",
              "ADR-0070"
            ],
            "tier": "personalisation",
            "where": "Cloudflare R2, in the EU"
          },
          {
            "control": "none; the records cannot be linked to you",
            "holds": "one record per question and one per contact confirmation, with no text; the record per question names what it was about in one word; while a message is being confirmed, a record of which fields you filled, the categories you picked and the page you started from, with a random id and no text; daily totals of requests per page",
            "n": 7,
            "name": "This site's records",
            "phase": 1,
            "retention": "records: 90 days, then monthly totals only, and deleted records stay restorable for 30 more days; the confirmation record: until the send ends, at most 10 minutes, then 24 hours more; daily totals: kept indefinitely",
            "source": [
              "ADR-0054",
              "ADR-0056",
              "ADR-0063",
              "ADR-0067",
              "ADR-0070",
              "ADR-0086",
              "ADR-0087"
            ],
            "tier": "necessary",
            "where": "Cloudflare D1 and the site's ledger, both in the EU"
          },
          {
            "control": "write to me and I delete it by hand",
            "holds": "your name if given, your address, your message and what you chose to include",
            "n": 8,
            "name": "A message you sent me",
            "phase": 1,
            "retention": "as long as our conversation needs it",
            "source": [
              "ADR-0054",
              "ADR-0066"
            ],
            "tier": "contact",
            "where": "my mailbox"
          },
          {
            "control": "none",
            "holds": "the message on its way to my mailbox",
            "n": 9,
            "name": "The mail transport",
            "phase": 1,
            "retention": "a preview for about 7 days, turned off where the setting exists; an activity log shown in the dashboard for up to 30 days",
            "source": [
              "ADR-0054",
              "ADR-0074"
            ],
            "tier": "contact",
            "where": "Cloudflare Email"
          }
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "slug": "privacy",
      "stale_after": "2027-01-18",
      "status": "published",
      "type": "processing",
      "withheld": []
    },
    "project:accreta": {
      "as_of": "2026-09-19",
      "data": {
        "claims": [
          {
            "evidence": [
              "source:accreta-npm",
              "source:accreta-atlas-repo"
            ],
            "id": "claim-published-npm",
            "statement": "Published on npm and installable by anyone; the companion repository installs it from the registry rather than from source, so a broken package fails there."
          },
          {
            "evidence": [
              "source:accreta-repo",
              "source:accreta-npm"
            ],
            "id": "claim-six-phases-in-a-month",
            "statement": "First commit to a published package with all six planned phases complete in about a month, across four releases."
          }
        ],
        "decisions": {
          "decision-compile-not-retrieve": {
            "skills": [
              "skill:knowledge-engineering"
            ]
          },
          "decision-drift-detection": {
            "skills": [
              "skill:knowledge-engineering"
            ]
          },
          "decision-mcp-beside-cli": {
            "skills": [
              "skill:mcp-servers"
            ]
          },
          "decision-provenance-to-revision": {
            "skills": [
              "skill:knowledge-engineering"
            ]
          }
        },
        "diagram": {
          "description": "Sources pinned to a revision are compiled by an agent, under its versioned rules, into wiki pages whose claims cite line range and revision. The pages are indexed in SQLite FTS5 and served to people through a CLI and to agents through an MCP server. When a source moves, drift names the pages now suspect.",
          "edges": [
            {
              "from": "sources",
              "to": "compile"
            },
            {
              "from": "compile",
              "to": "pages"
            },
            {
              "from": "pages",
              "to": "index"
            },
            {
              "from": "index",
              "to": "cli"
            },
            {
              "from": "index",
              "to": "mcp"
            }
          ],
          "loop": {
            "from": "sources",
            "label": "a source moves → drift names the pages now suspect",
            "to": "pages"
          },
          "nodes": [
            {
              "id": "sources",
              "label": "Sources",
              "note": "repos, docs, RFCs, pinned to a revision"
            },
            {
              "id": "compile",
              "label": "Agent compiles",
              "note": "under the constitution, its versioned rules"
            },
            {
              "emphasis": true,
              "id": "pages",
              "label": "Wiki pages",
              "note": "every claim cites its line range and revision"
            },
            {
              "id": "index",
              "label": "Index",
              "note": "SQLite FTS5"
            },
            {
              "id": "cli",
              "label": "CLI",
              "note": "a person at a terminal"
            },
            {
              "id": "mcp",
              "label": "MCP server",
              "note": "any agent"
            }
          ],
          "title": "How accreta works"
        },
        "key_figures": [
          {
            "claim": "claim-six-phases-in-a-month",
            "label": "planned phases shipped",
            "value": "6/6"
          },
          {
            "claim": "claim-six-phases-in-a-month",
            "label": "first commit to a published package",
            "value": "≈1 mo"
          },
          {
            "claim": "claim-six-phases-in-a-month",
            "label": "releases",
            "value": "4"
          },
          {
            "claim": "claim-published-npm",
            "label": "installable by anyone; atlas installs it from the registry",
            "value": "npm"
          }
        ],
        "kind": "case-study",
        "radar": {
          "claim-six-phases-in-a-month": "How was it built so quickly?",
          "decision-compile-not-retrieve": "Why compile a wiki instead of using RAG?",
          "decision-drift-detection": "How does it know a page has gone stale?",
          "decision-mcp-beside-cli": "Why ship an MCP server as well as a CLI?",
          "decision-provenance-to-revision": "Why cite sources down to the revision?"
        },
        "role_name": "Author and maintainer",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "built end to end through coding agents, six phases in about a month"
          },
          {
            "id": "skill:context-engineering",
            "note": "the constitution — the agent's operating rules, versioned as a template"
          },
          {
            "id": "skill:typescript"
          },
          {
            "id": "skill:mcp-servers",
            "note": "ships an MCP server beside the CLI"
          },
          {
            "id": "skill:knowledge-engineering",
            "note": "the provenance and drift model"
          }
        ],
        "sources": [
          "source:accreta-repo",
          "source:accreta-npm"
        ],
        "start": "2026-08",
        "tagline": "A knowledge base an agent writes, cited down to the revision.",
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "Open-source tooling for agent-maintained knowledge bases with provenance and drift detection. TypeScript, MCP server, SQLite FTS5.",
      "slug": "accreta",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "A knowledge base an AI agent writes and maintains, where every claim cites its source down to the revision and a drift command says which pages a source change has made suspect.",
      "title": "accreta",
      "type": "project",
      "withheld": []
    },
    "project:accreta-atlas": {
      "as_of": "2026-09-19",
      "data": {
        "category": "test-bed",
        "claims": [
          {
            "evidence": [
              "source:accreta-atlas-repo"
            ],
            "id": "claim-rfc-corpus",
            "statement": "The corpus is the IETF RFC series, vendored in the repository; a published RFC never changes, so its revision stays frozen and drift can run in CI."
          },
          {
            "evidence": [
              "source:accreta-atlas-repo"
            ],
            "id": "claim-drift-goes-red",
            "statement": "CI installs accreta from npm and runs reindex, lint and drift as real assertions, with fixtures built to make drift go red."
          }
        ],
        "key_figures": [
          {
            "claim": "claim-rfc-corpus",
            "label": "IETF series as the corpus",
            "value": "RFC"
          },
          {
            "claim": "claim-drift-goes-red",
            "label": "runs drift, with fixtures built to make it go red",
            "value": "CI"
          }
        ],
        "kind": "entry",
        "role_name": "Author",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "drift detection running in CI as a real assertion"
          },
          {
            "id": "skill:typescript"
          },
          {
            "id": "skill:knowledge-engineering",
            "note": "a corpus large enough to be a real test"
          }
        ],
        "sources": [
          "source:accreta-atlas-repo"
        ],
        "start": "2026-08",
        "tagline": "accreta over the IETF RFC series, installed from npm.",
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "A knowledge base built by an agent over the IETF RFC series, and the integration test bed for accreta.",
      "lead": {
        "markdown": "The worked example inside accreta runs from a checkout and deliberately skips `drift`, so it can never prove that drift detection is more than a no-op. This repository is the other half: it installs the published package, runs `reindex`, `lint` and `drift` as real assertions, and carries fixtures whose job is to make `drift` go red.",
        "text": "The worked example inside accreta runs from a checkout and deliberately skips drift, so it can never prove that drift detection is more than a no-op. This repository is the other half: it installs the published package, runs reindex, lint and drift as real assertions, and carries fixtures whose job is to make drift go red."
      },
      "slug": "accreta-atlas",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "The test bed where accreta is exercised the way a user meets it — installed from npm, over the IETF RFC series, with drift detection running in CI against fixtures built to make it fail.",
      "title": "accreta-atlas",
      "type": "project",
      "withheld": []
    },
    "project:agentforge": {
      "as_of": "2026-09-19",
      "data": {
        "category": "architecture",
        "claims": [
          {
            "evidence": [
              "source:agentforge-repo"
            ],
            "id": "claim-six-guardrail-layers",
            "statement": "The design places safety policy in six guardrail layers.",
            "unit": "guardrail layers",
            "value": 6
          },
          {
            "evidence": [
              "source:agentforge-repo"
            ],
            "id": "claim-design-only",
            "statement": "The repository holds architecture decision records and subsystem specifications, with no implementation behind them."
          }
        ],
        "key_figures": [
          {
            "claim": "claim-six-guardrail-layers",
            "label": "guardrail layers in the design",
            "value": "6"
          },
          {
            "claim": "claim-design-only",
            "label": "phase only; no implementation behind it",
            "value": "Design"
          }
        ],
        "kind": "entry",
        "role_name": "Author",
        "skills": [
          {
            "id": "skill:agent-orchestration"
          },
          {
            "id": "skill:multi-tenant-saas"
          },
          {
            "id": "skill:guardrails"
          }
        ],
        "sources": [
          "source:agentforge-repo"
        ],
        "start": "2026-02",
        "tagline": "A multi-tenant platform for multi-agent systems, on paper.",
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "Architecture and decision records for a multi-tenant multi-agent orchestration platform. Design phase, not implemented.",
      "lead": {
        "markdown": "Architecture decision records and subsystem specifications for running LLM agents at scale: versioned system prompts, agent teams, safety policies across six guardrail layers and OpenTelemetry tracing throughout. The repository is explicit that it is a design, with no implementation behind it — it is included here as design work, not as a shipped system.",
        "text": "Architecture decision records and subsystem specifications for running LLM agents at scale: versioned system prompts, agent teams, safety policies across six guardrail layers and OpenTelemetry tracing throughout. The repository is explicit that it is a design, with no implementation behind it — it is included here as design work, not as a shipped system."
      },
      "slug": "agentforge",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "A design-phase architecture for a multi-tenant platform for multi-agent systems — hierarchical supervisor topology, six guardrail layers, per-tenant isolation and end-to-end tracing.",
      "title": "AgentForge",
      "type": "project",
      "withheld": []
    },
    "project:claude-account-switcher": {
      "as_of": "2026-09-19",
      "data": {
        "category": "tool",
        "claims": [
          {
            "evidence": [
              "source:claude-account-switcher-repo"
            ],
            "id": "claim-built-in-a-day",
            "statement": "Built, tested and shipped with CI in a single day."
          },
          {
            "evidence": [
              "source:claude-account-switcher-repo"
            ],
            "id": "claim-nothing-patched",
            "statement": "Nothing in Claude Code is patched; the tool uses Claude Code's own process-wrapper setting and its config-directory variable."
          }
        ],
        "key_figures": [
          {
            "claim": "claim-built-in-a-day",
            "label": "built, tested and shipped with CI",
            "value": "1 day"
          },
          {
            "claim": "claim-nothing-patched",
            "label": "patches to Claude Code; it uses its own settings",
            "value": "0"
          }
        ],
        "kind": "entry",
        "radar": {
          "claim-built-in-a-day": "What made a one-day build possible?"
        },
        "role_name": "Author",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "tooling for running coding agents across projects"
          },
          {
            "id": "skill:developer-tooling"
          }
        ],
        "sources": [
          "source:claude-account-switcher-repo"
        ],
        "start": "2026-09",
        "tagline": "One Claude Code account per project, shown like a git branch."
      },
      "description": "Per-project Claude Code account switching on macOS, driven by path.",
      "lead": {
        "markdown": "Claude Code keeps one login per machine but isolates credentials per `CLAUDE_CONFIG_DIR`, and on macOS that variable decides which Keychain service is used. The tool turns that into per-directory account selection, so the work account is used on work repositories and the personal one everywhere else, with both staying logged in.",
        "text": "Claude Code keeps one login per machine but isolates credentials per CLAUDE_CONFIG_DIR, and on macOS that variable decides which Keychain service is used. The tool turns that into per-directory account selection, so the work account is used on work repositories and the personal one everywhere else, with both staying logged in."
      },
      "slug": "claude-account-switcher",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "One Claude Code account per project, chosen from the directory you are in and shown in the VS Code status bar like a git branch.",
      "title": "claude-account-switcher",
      "type": "project",
      "withheld": []
    },
    "project:coding-agent-sync": {
      "as_of": "2026-09-19",
      "data": {
        "category": "tool",
        "claims": [
          {
            "evidence": [
              "source:coding-agent-sync-repo"
            ],
            "id": "claim-one-manifest",
            "statement": "One agents.yaml manifest generates the instruction files for Codex, Claude Code, Gemini CLI, GitHub Copilot, Cursor, Windsurf, Continue and Cline."
          },
          {
            "evidence": [
              "source:coding-agent-sync-repo"
            ],
            "id": "claim-doctor-fails-ci",
            "statement": "The doctor command validates the manifest and exits non-zero on drift, so CI catches it."
          }
        ],
        "key_figures": [
          {
            "claim": "claim-one-manifest",
            "label": "manifest generating every agent's instruction file",
            "value": "1"
          },
          {
            "claim": "claim-doctor-fails-ci",
            "label": "fails when the generated files drift",
            "value": "CI"
          }
        ],
        "kind": "entry",
        "role_name": "Author",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "the manifest that keeps every agent's instructions in step"
          },
          {
            "id": "skill:context-engineering",
            "note": "one source of truth for what every coding agent is told"
          },
          {
            "id": "skill:developer-tooling"
          },
          {
            "id": "skill:python-fastapi",
            "note": "written in Python"
          }
        ],
        "sources": [
          "source:coding-agent-sync-repo"
        ],
        "start": "2026-04",
        "tagline": "One agents.yaml for every coding agent's instructions.",
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "Generate CLAUDE.md, AGENTS.md, .cursor/rules and the rest from a single manifest.",
      "lead": {
        "markdown": "Every coding agent wants its own instruction file, and keeping six of them in step by hand guarantees they diverge. The manifest is the source of truth; `import` consolidates what a repository already has, `sync` regenerates the outputs, and `doctor` exits non-zero on drift so CI catches it.",
        "text": "Every coding agent wants its own instruction file, and keeping six of them in step by hand guarantees they diverge. The manifest is the source of truth; import consolidates what a repository already has, sync regenerates the outputs, and doctor exits non-zero on drift so CI catches it."
      },
      "slug": "coding-agent-sync",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "One agents.yaml manifest generating the instruction file every coding agent expects, with a doctor command that fails CI when they drift apart.",
      "title": "coding-agent-sync",
      "type": "project",
      "withheld": []
    },
    "project:disk-reclaim": {
      "as_of": "2026-09-19",
      "data": {
        "category": "tool",
        "claims": [
          {
            "evidence": [
              "source:disk-reclaim-repo"
            ],
            "id": "claim-manual-reclaim",
            "statement": "The manual investigation the tool came from reclaimed 118 GB in two hours, on a machine down to 1.4 GB free out of 460 GB.",
            "unit": "GB",
            "value": 118
          },
          {
            "evidence": [
              "source:disk-reclaim-repo"
            ],
            "id": "claim-three-surfaces",
            "statement": "Ships as a SwiftUI app, a CLI and an MCP server over one shared core.",
            "unit": "surfaces",
            "value": 3
          }
        ],
        "key_figures": [
          {
            "claim": "claim-manual-reclaim",
            "label": "reclaimed by hand in two hours; where the tool began",
            "value": "118 GB"
          },
          {
            "claim": "claim-three-surfaces",
            "label": "surfaces over one core: app, CLI, MCP server",
            "value": "3"
          }
        ],
        "kind": "entry",
        "radar": {
          "claim-manual-reclaim": "Where did all that space go?"
        },
        "role_name": "Author",
        "skills": [
          {
            "id": "skill:swift-swiftui"
          },
          {
            "id": "skill:mcp-servers",
            "note": "the same core exposed to an agent"
          },
          {
            "id": "skill:developer-tooling"
          }
        ],
        "sources": [
          "source:disk-reclaim-repo"
        ],
        "start": "2026-07",
        "tagline": "Makes a dev machine's disk readable and reclaims space safely."
      },
      "description": "Disk analysis and safe space reclamation for macOS development machines.",
      "lead": {
        "markdown": "It started as a manual operation on 2026-07-31, recorded immutably in the repository's brief: the numbers are measured and the traps that investigation fell into became test cases rather than hypotheses.",
        "text": "It started as a manual operation on 2026-07-31, recorded immutably in the repository's brief: the numbers are measured and the traps that investigation fell into became test cases rather than hypotheses."
      },
      "slug": "disk-reclaim",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "A macOS tool that makes a development machine's disk occupancy readable and reclaims space safely, shipped as a SwiftUI app, a CLI and an MCP server over one shared core.",
      "title": "disk-reclaim",
      "type": "project",
      "withheld": []
    },
    "project:praxis": {
      "as_of": "2026-09-19",
      "data": {
        "claims": [
          {
            "evidence": [
              "source:praxis-repo"
            ],
            "id": "claim-four-budget-dimensions",
            "statement": "The kernel enforces budgets in four dimensions — wall-clock time, LLM tokens, tool-call count and estimated cost — and a breach ends the invocation.",
            "unit": "budget dimensions",
            "value": 4
          },
          {
            "evidence": [
              "source:praxis-repo"
            ],
            "id": "claim-mandatory-telemetry",
            "statement": "OpenTelemetry spans are a framework guarantee, emitted for every invocation without the application opting in."
          },
          {
            "evidence": [
              "source:praxis-repo"
            ],
            "id": "claim-apache-licence",
            "statement": "Released under Apache 2.0 and published on pkg.go.dev, with CI on the repository."
          }
        ],
        "decisions": {
          "decision-guardrails-in-kernel": {
            "skills": [
              "skill:guardrails"
            ]
          },
          "decision-mandatory-telemetry": {
            "skills": [
              "skill:llm-observability"
            ]
          },
          "decision-provider-agnostic": {
            "skills": [
              "skill:agent-orchestration"
            ]
          }
        },
        "diagram": {
          "description": "An invocation passes a policy pre-hook, which can deny it, then calls the model. A tool decision follows. Tool calls run, their output passes a filter chain, and the model continues; more tool calls loop back to the decision. At end of turn a post-hook runs and the invocation completes. A breach of any budget dimension ends it as BudgetExceeded instead.",
          "edges": [
            {
              "from": "pre-hook",
              "to": "llm-call"
            },
            {
              "from": "llm-call",
              "to": "tool-decision"
            },
            {
              "from": "tool-decision",
              "to": "tool-call"
            },
            {
              "from": "tool-call",
              "to": "post-tool-filter"
            },
            {
              "from": "post-tool-filter",
              "to": "continuation"
            },
            {
              "from": "continuation",
              "to": "post-hook"
            },
            {
              "from": "tool-decision",
              "to": "post-hook"
            },
            {
              "from": "llm-call",
              "to": "budget-exceeded"
            }
          ],
          "loop": {
            "from": "continuation",
            "label": "more tools",
            "to": "tool-decision"
          },
          "nodes": [
            {
              "emphasis": true,
              "id": "pre-hook",
              "label": "PreHook",
              "note": "policy allows or denies"
            },
            {
              "id": "llm-call",
              "label": "LLMCall"
            },
            {
              "id": "tool-decision",
              "label": "ToolDecision"
            },
            {
              "id": "tool-call",
              "label": "ToolCall"
            },
            {
              "id": "post-tool-filter",
              "label": "PostToolFilter",
              "note": "filter chain on tool output"
            },
            {
              "id": "continuation",
              "label": "LLMContinuation"
            },
            {
              "id": "post-hook",
              "label": "PostHook",
              "note": "then Completed"
            },
            {
              "id": "budget-exceeded",
              "label": "BudgetExceeded",
              "note": "any of four dimensions breached"
            }
          ],
          "title": "The Praxis invocation state machine"
        },
        "key_figures": [
          {
            "claim": "claim-four-budget-dimensions",
            "label": "budget enforcement: time, tokens, tool calls, cost",
            "value": "4-D"
          },
          {
            "claim": "claim-mandatory-telemetry",
            "label": "mandatory, not optional",
            "value": "OTel"
          },
          {
            "claim": "claim-apache-licence",
            "label": "Apache licence, published on pkg.go.dev",
            "value": "2.0"
          }
        ],
        "kind": "case-study",
        "radar": {
          "decision-guardrails-in-kernel": "Why put the guardrails in the framework, not the app?",
          "decision-mandatory-telemetry": "Why can't telemetry be turned off?",
          "decision-provider-agnostic": "Can I swap the model provider?"
        },
        "role_name": "Maintainer",
        "skills": [
          {
            "id": "skill:go"
          },
          {
            "id": "skill:agent-orchestration",
            "note": "the invocation kernel"
          },
          {
            "id": "skill:llm-observability",
            "note": "OpenTelemetry is mandatory, not optional"
          },
          {
            "id": "skill:guardrails",
            "note": "policy hooks and filter chains at every security-sensitive boundary"
          }
        ],
        "sources": [
          "source:praxis-repo"
        ],
        "tagline": "A Go runtime for LLM agents, guardrails in the kernel.",
        "topics": [
          "topic:agentic-ai"
        ]
      },
      "description": "Production-grade Go runtime for LLM agent orchestration with enterprise guardrails as framework-level guarantees.",
      "slug": "praxis",
      "stale_after": "2026-12-18",
      "status": "published",
      "summary": "A Go library for orchestrating LLM agents with the guardrails built into the kernel — typed invocation state machine, policy hooks at every sensitive boundary, budget enforcement and mandatory telemetry.",
      "title": "Praxis",
      "type": "project",
      "withheld": []
    },
    "project:radicas": {
      "as_of": "2026-09-18",
      "data": {
        "claims": [
          {
            "approximate": true,
            "evidence": [
              "source:github-profile"
            ],
            "id": "claim-adr-count",
            "statement": "Around thirty ADRs are written down behind the product, each with its reasoning and what would change it.",
            "unit": "ADRs",
            "value": 30
          },
          {
            "evidence": [
              "experience:founder-in-residence-reef",
              "experience:founder-in-residence-reef#highlight-zero-to-users"
            ],
            "id": "claim-problem-to-first-users",
            "statement": "Went from problem to first users inside the five-month Reef by Vento programme.",
            "unit": "months",
            "value": 5
          },
          {
            "evidence": [
              "experience:founder-in-residence-reef"
            ],
            "id": "claim-backed-by-vento",
            "statement": "Built and backed inside Reef, the venture-building programme of Vento, Exor's early-stage VC arm."
          }
        ],
        "decisions": {
          "decision-eu-native-hosting": {
            "skills": [
              "skill:terraform"
            ]
          },
          "decision-single-artifact-deployment": {
            "skills": [
              "skill:multi-tenant-saas"
            ]
          },
          "decision-span-to-invoice-join": {
            "skills": [
              "skill:llm-observability",
              "skill:clickhouse"
            ]
          }
        },
        "diagram": {
          "description": "OpenTelemetry gen_ai spans are priced in real time from a price book, giving an estimated cost per call. The provider's invoice arrives days later as FOCUS 1.3 data, and each span is reconciled against its invoice line items, so the real-time estimate is corrected by the authoritative figure. The result is cost per feature and per tenant.",
          "edges": [
            {
              "from": "spans",
              "to": "estimate"
            },
            {
              "from": "estimate",
              "to": "reconcile"
            },
            {
              "from": "invoice",
              "to": "reconcile"
            },
            {
              "from": "reconcile",
              "to": "cost"
            }
          ],
          "nodes": [
            {
              "id": "spans",
              "label": "gen_ai spans",
              "note": "from OpenTelemetry"
            },
            {
              "id": "estimate",
              "label": "Real-time estimate",
              "note": "priced from a price book"
            },
            {
              "id": "invoice",
              "label": "Provider invoice",
              "note": "FOCUS 1.3, days later"
            },
            {
              "emphasis": true,
              "id": "reconcile",
              "label": "Reconciliation",
              "note": "span by span against line items"
            },
            {
              "id": "cost",
              "label": "Cost per feature",
              "note": "and per tenant"
            }
          ],
          "title": "How Radicas reconciles cost"
        },
        "key_figures": [
          {
            "claim": "claim-backed-by-vento",
            "label": "backed by Vento, Exor's early-stage VC arm",
            "value": "Vento"
          },
          {
            "claim": "claim-problem-to-first-users",
            "label": "problem to first users",
            "value": "5 mo"
          }
        ],
        "kind": "case-study",
        "org": "org:reef-by-vento",
        "role_name": "Founder and engineer",
        "skills": [
          {
            "id": "skill:agent-assisted-delivery",
            "note": "problem to first users in a five-month programme, around thirty ADRs behind it"
          },
          {
            "id": "skill:finops-for-ai",
            "note": "the product itself"
          },
          {
            "id": "skill:llm-observability",
            "note": "ingests and interprets OpenTelemetry gen_ai spans"
          },
          {
            "id": "skill:python-fastapi",
            "note": "backend services"
          },
          {
            "id": "skill:go",
            "note": "OpenTelemetry collector"
          },
          {
            "id": "skill:clickhouse",
            "note": "span and cost store"
          },
          {
            "id": "skill:terraform",
            "note": "Helm and Terraform on Hetzner k3s"
          },
          {
            "id": "skill:multi-tenant-saas",
            "note": "one artifact across SaaS, self-host and BYOC"
          }
        ],
        "sources": [
          "source:radicas-site"
        ],
        "start": "2026-02",
        "tagline": "What an agentic AI feature costs, and what it returns."
      },
      "description": "FinOps for AI — feature-level unit economics from OpenTelemetry gen_ai spans reconciled against FOCUS invoice data.",
      "slug": "radicas",
      "stale_after": "2026-12-17",
      "status": "published",
      "summary": "A FinOps platform that measures what an agentic AI feature costs and what it returns, by reconciling real-time OpenTelemetry spans against the invoice that arrives days later.",
      "title": "Radicas",
      "type": "project",
      "withheld": [
        {
          "reason": "proprietary",
          "scope": [
            "project:radicas#decision-span-to-invoice-join",
            "project:radicas#decision-eu-native-hosting",
            "project:radicas#decision-single-artifact-deployment"
          ],
          "topic": "source code"
        },
        {
          "reason": "commercially confidential",
          "topic": "customer names and revenue figures"
        },
        {
          "reason": "commercially sensitive while the product is live",
          "scope": [
            "project:radicas#decision-span-to-invoice-join",
            "project:radicas#decision-eu-native-hosting",
            "project:radicas#decision-single-artifact-deployment"
          ],
          "topic": "design rationale — the alternatives weighed and why they were rejected"
        }
      ]
    },
    "site:analytics-observability": {
      "data": {
        "claim_rows": [
          "C2",
          "C4",
          "C18",
          "C19"
        ],
        "derived_from": [
          "docs/deep-dives/08-seeing-and-judging.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/decisions/ADR-0019-accessibility-performance-budgets.md",
          "docs/decisions/ADR-0037-client-event-vocabulary.md",
          "docs/decisions/ADR-0052-abuse-bots-alerts.md",
          "docs/decisions/ADR-0053-consent-tier-matrix.md",
          "docs/decisions/ADR-0054-retention-redaction-schedule.md",
          "docs/decisions/ADR-0056-turn-trace-schema.md",
          "docs/decisions/ADR-0057-metric-sheet-dashboard-phases.md",
          "docs/decisions/ADR-0058-golden-set-composition-upkeep.md",
          "docs/decisions/ADR-0059-grading-stack-judge-calibration.md",
          "docs/decisions/ADR-0060-eval-gates-ci.md",
          "docs/decisions/ADR-0061-feedback-signal-review-cadence.md",
          "docs/decisions/ADR-0070-ledger-memory-trace-stores.md",
          "docs/decisions/ADR-0085-edge-adds-nothing.md",
          "docs/decisions/ADR-0086-page-views-from-zone-analytics.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md"
        ],
        "sources": [
          "source:adr-0019",
          "source:adr-0037",
          "source:adr-0052",
          "source:adr-0053",
          "source:adr-0054",
          "source:adr-0056",
          "source:adr-0057",
          "source:adr-0058",
          "source:adr-0059",
          "source:adr-0060",
          "source:adr-0061",
          "source:adr-0070",
          "source:adr-0085",
          "source:adr-0086",
          "source:adr-0087"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "How the portfolio agent is observed and judged. One record per turn with no free text, a metric sheet with denominators, and a test set that gates changes.",
      "lead": {
        "markdown": "Observability for an agent usually means logging everything and deciding later what to look at. Here the decision came first: every number the brief asks for was written as an expression over named fields, and only those fields exist. The result is a system I can debug and cost without ever reading what anybody asked. What that means for your privacy is on [Guardrails, privacy and security](/how-it-works/guardrails-privacy-security). This page is about what the numbers are and what they cannot tell me.",
        "text": "Observability for an agent usually means logging everything and deciding later what to look at. Here the decision came first: every number the brief asks for was written as an expression over named fields, and only those fields exist. The result is a system I can debug and cost without ever reading what anybody asked. What that means for your privacy is on Guardrails, privacy and security. This page is about what the numbers are and what they cannot tell me."
      },
      "slug": "analytics-observability",
      "status": "published",
      "summary": "The owner can see what each question cost, which layer answered it, which tools failed and which topics had no answer, from one record per question made only of ids, fixed values and numbers. A printed metric sheet and four alerts do the rest.",
      "title": "Analytics and observability",
      "type": "site",
      "withheld": []
    },
    "site:guardrails-privacy-security": {
      "data": {
        "canned": [
          {
            "anchor": "site:guardrails-privacy-security#section-what-the-site-remembers",
            "answer": {
              "en": "One record per question, with no text in it: ids, counts, costs, timings, which pages were cited, the question's language, what it is about in one of nine words, and two scores for how likely it is to be off-topic or an attempt to change the rules. Your address is kept only in a scrambled form whose key changes daily. The conversation itself stays in your tab and is gone when you close it.",
              "it": "Un record per domanda, senza alcun testo: id, conteggi, costi, tempi, le pagine citate, la lingua della domanda, il suo argomento in una di nove parole e due punteggi, quanto è probabile che sia fuori tema o un tentativo di cambiare le regole. Il tuo indirizzo IP è conservato solo come hash, con una chiave che cambia ogni giorno. La conversazione resta nella tua scheda e sparisce quando la chiudi."
            },
            "id": "what-the-site-stores",
            "questions": {
              "en": [
                "What does this site store about me?",
                "Do you save my questions?",
                "Are my conversations stored?"
              ],
              "it": [
                "Cosa memorizza questo sito su di me?",
                "Salvate le mie domande?",
                "Le mie conversazioni vengono salvate?"
              ]
            }
          },
          {
            "anchor": "site:guardrails-privacy-security#section-what-stays-on-your-device",
            "answer": {
              "en": "No cookies, from this site or from its host. On /ask, your conversation is kept in the tab's session storage and is gone when you close it. There is no consent banner because there is nothing to consent to.",
              "it": "Nessun cookie, né del sito né del suo host. Su /ask la conversazione è tenuta nel session storage della scheda e sparisce quando la chiudi. Non c'è un banner di consenso perché non c'è nulla a cui acconsentire."
            },
            "id": "cookies",
            "questions": {
              "en": [
                "Does this site use cookies?",
                "Why is there no cookie banner?"
              ],
              "it": [
                "Questo sito usa i cookie?",
                "Perché non c'è un banner dei cookie?"
              ]
            }
          },
          {
            "anchor": "site:guardrails-privacy-security#section-what-leaves-it",
            "answer": {
              "en": "To two companies. TypeSafe decides whether the question is about Francesco. OpenAI writes the answer, and receives the question, the earlier turns and the page you are on. The privacy page lists what each receives and keeps, as read from their terms.",
              "it": "A due aziende. TypeSafe decide se la domanda riguarda Francesco. OpenAI scrive la risposta e riceve la domanda, i turni precedenti e la pagina su cui ti trovi. La pagina sulla privacy elenca cosa riceve e conserva ciascuna, come letto dai loro termini."
            },
            "id": "where-questions-go",
            "questions": {
              "en": [
                "Where do my questions go?",
                "Who sees what I ask the assistant?"
              ],
              "it": [
                "Dove vanno le mie domande?",
                "Chi vede quello che chiedo all'assistente?"
              ]
            }
          }
        ],
        "claim_rows": [
          "C1",
          "C3",
          "C4",
          "C5",
          "C6",
          "C7",
          "C8",
          "C9",
          "C10",
          "C11",
          "C12",
          "C13",
          "C22"
        ],
        "derived_from": [
          "docs/decisions/ADR-0019-accessibility-performance-budgets.md",
          "docs/decisions/ADR-0032-ui-actions-catalogue-authorisation.md",
          "docs/decisions/ADR-0033-external-class-confirmation-protocol.md",
          "docs/decisions/ADR-0039-corpus-projection-freshness-citation.md",
          "docs/decisions/ADR-0042-prompt-architecture-trust-fences.md",
          "docs/decisions/ADR-0053-consent-tier-matrix.md",
          "docs/decisions/ADR-0054-retention-redaction-schedule.md",
          "docs/decisions/ADR-0055-threat-model-disclosure-boundary.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md",
          "docs/decisions/ADR-0070-ledger-memory-trace-stores.md",
          "docs/decisions/ADR-0071-ask-without-a-query-string.md",
          "docs/decisions/ADR-0073-residency-processors-cost.md",
          "docs/decisions/ADR-0082-jev-slots-and-processor-route.md",
          "docs/decisions/ADR-0083-privacy-notice-in-house.md",
          "docs/decisions/ADR-0085-edge-adds-nothing.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md",
          "docs/deep-dives/08-seeing-and-judging.md"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "How francescofiore.dev handles privacy and security. No cookies, no stored visitor text, two named providers, and injection defences that rest on what the system cannot do.",
      "lead": {
        "markdown": "Most of this site's defences are things it cannot do. An answer cannot contain a link. The assistant has no tool that sends a message. Your words are never written to a store this site owns, because none of its records has a field that could hold them. A capability that does not exist cannot be talked into misbehaving, which is why I prefer removing one to guarding it.",
        "text": "Most of this site's defences are things it cannot do. An answer cannot contain a link. The assistant has no tool that sends a message. Your words are never written to a store this site owns, because none of its records has a field that could hold them. A capability that does not exist cannot be talked into misbehaving, which is why I prefer removing one to guarding it."
      },
      "slug": "guardrails-privacy-security",
      "status": "published",
      "summary": "Most of this site's defences are things it cannot do. An answer cannot contain a link, the assistant has no tool that sends a message, and no record it keeps has a field that could hold your words.",
      "title": "Guardrails, privacy and security",
      "type": "site",
      "withheld": []
    },
    "site:knowledge-layer": {
      "data": {
        "canned": [
          {
            "anchor": "site:knowledge-layer#section-designed-in-the-open",
            "answer": {
              "en": "It was designed before it was built. Every design decision is an ADR, written before the code and kept with the content in a private repository, so the code is not public. The content is Markdown and YAML compiled into one file, kb.json, published at /kb.json, and the pages, this assistant and search engines all read that same file. The How it works section has a page for each part of the system.",
              "it": "È stato progettato prima di essere costruito. Ogni decisione di progetto è un ADR, scritto prima del codice e tenuto insieme ai contenuti in un repository privato, quindi il codice non è pubblico. I contenuti sono Markdown e YAML compilati in un unico file, kb.json, pubblicato su /kb.json, e le pagine, questo assistente e i motori di ricerca leggono tutti lo stesso file. La sezione How it works ha una pagina per ogni parte del sistema."
            },
            "id": "how-the-site-was-built",
            "questions": {
              "en": [
                "How did you build this site?",
                "How does this site work?",
                "Is this site open source?"
              ],
              "it": [
                "Come hai costruito questo sito?",
                "Come funziona questo sito?",
                "Il codice di questo sito è pubblico?"
              ]
            }
          }
        ],
        "derived_from": [
          "docs/deep-dives/01-content-model.md",
          "docs/decisions/ADR-0001-docs-first-logical-components.md",
          "docs/decisions/ADR-0002-source-format-compiled-artefact.md",
          "docs/decisions/ADR-0003-knowledge-base-toolchain.md",
          "docs/decisions/ADR-0004-entity-catalogue-relations-evidence.md",
          "docs/decisions/ADR-0005-visibility-overlay-leak-testing.md",
          "docs/decisions/ADR-0006-ids-anchors-slugs-redirects.md",
          "docs/decisions/ADR-0007-validity-staleness-invalidation.md",
          "docs/decisions/ADR-0008-english-only-content.md",
          "docs/decisions/ADR-0009-editorial-loop.md",
          "docs/decisions/ADR-0014-page-projection-and-copy.md"
        ],
        "sources": [
          "source:adr-0001",
          "source:adr-0002",
          "source:adr-0003",
          "source:adr-0004",
          "source:adr-0005",
          "source:adr-0006",
          "source:adr-0007",
          "source:adr-0008",
          "source:adr-0009",
          "source:adr-0014"
        ],
        "verified_commit": "92db2f3c7ea8d086ccdb1b9c52a2d65c9f81412a"
      },
      "description": "How the portfolio's content is modelled. Markdown and YAML in git, compiled into one versioned artefact that every page, the agent and the crawlers read.",
      "lead": {
        "markdown": "One file is the contract. Content is written once, as Markdown and YAML in the repository's `content/` folder. A compiler checks it and emits `kb.json`, with the images it references beside it, and nothing else is read by anyone. The pages are built from it, the assistant is grounded in it, the structured data and the CV are views of it, and it is published at a stable URL for anything that wants the whole thing. If two surfaces ever disagreed, one of them would have to be reading something else, and there is nothing else to read.",
        "text": "One file is the contract. Content is written once, as Markdown and YAML in the repository's content/ folder. A compiler checks it and emits kb.json, with the images it references beside it, and nothing else is read by anyone. The pages are built from it, the assistant is grounded in it, the structured data and the CV are views of it, and it is published at a stable URL for anything that wants the whole thing. If two surfaces ever disagreed, one of them would have to be reading something else, and there is nothing else to read."
      },
      "slug": "knowledge-layer",
      "status": "published",
      "summary": "Everything the pages, the assistant and the crawlers say about Francesco comes from one compiled file, kb.json, built from Markdown and YAML kept in a private repository and published as /kb.json.",
      "title": "Knowledge layer",
      "type": "site",
      "withheld": []
    },
    "site:known-limits": {
      "data": {
        "claim_rows": [
          "C5",
          "C12",
          "C17",
          "C18",
          "C19",
          "C20",
          "C23"
        ],
        "derived_from": [
          "docs/decisions/ADR-0036-client-storage-context-payload.md",
          "docs/decisions/ADR-0045-consented-identifier-memory-store.md",
          "docs/decisions/ADR-0053-consent-tier-matrix.md",
          "docs/decisions/ADR-0054-retention-redaction-schedule.md",
          "docs/decisions/ADR-0055-threat-model-disclosure-boundary.md",
          "docs/decisions/ADR-0057-metric-sheet-dashboard-phases.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md",
          "docs/decisions/ADR-0073-residency-processors-cost.md",
          "docs/decisions/ADR-0081-scope-gate-on-jev.md",
          "docs/decisions/ADR-0082-jev-slots-and-processor-route.md",
          "docs/decisions/ADR-0083-privacy-notice-in-house.md",
          "docs/decisions/ADR-0086-page-views-from-zone-analytics.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md",
          "docs/deep-dives/15-disclosure-pages.md"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "The limits of francescofiore.dev stated plainly. No external security review, no legal review, one injection run per model, estimated page counts, and the privacy trade-offs chosen on purpose.",
      "slug": "known-limits",
      "status": "published",
      "summary": "What this site has not proved, and what it gave up on purpose, knowing the cost.",
      "title": "Known limits and design decisions",
      "type": "site",
      "withheld": []
    },
    "site:memory-personalisation": {
      "data": {
        "canned": [
          {
            "anchor": "site:memory-personalisation#section-nothing-outlives-the-tab",
            "answer": {
              "en": "No. I have no memory of visitors at this stage. This conversation is kept only in your browser tab, and it is gone when you close the tab. When memory arrives, it will stay off until you turn it on, and you will be able to see it, reset it and delete it.",
              "it": "No. In questa fase non ho memoria dei visitatori. Questa conversazione resta solo nella scheda del browser e sparisce quando la chiudi. Quando arriverà la memoria, resterà spenta finché non la attivi tu, e potrai vederla, azzerarla e cancellarla."
            },
            "id": "does-it-remember-me",
            "questions": {
              "en": [
                "Do you remember me?",
                "Will you remember this conversation?",
                "Do you know who I am?"
              ],
              "it": [
                "Ti ricordi di me?",
                "Ti ricorderai di questa conversazione?",
                "Sai chi sono?"
              ]
            }
          }
        ],
        "claim_rows": [
          "C17"
        ],
        "derived_from": [
          "docs/deep-dives/06-memory.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/decisions/ADR-0035-state-partition-thread-continuity.md",
          "docs/decisions/ADR-0036-client-storage-context-payload.md",
          "docs/decisions/ADR-0044-context-assembly-history-depth.md",
          "docs/decisions/ADR-0045-consented-identifier-memory-store.md",
          "docs/decisions/ADR-0046-memory-record-interest-vocabulary.md",
          "docs/decisions/ADR-0047-memory-lifecycle-synthesis-deletion.md",
          "docs/decisions/ADR-0048-optin-moment-memory-view.md",
          "docs/decisions/ADR-0049-memory-ordering-no-cls.md",
          "docs/decisions/ADR-0056-turn-trace-schema.md"
        ],
        "sources": [
          "source:adr-0035",
          "source:adr-0036",
          "source:adr-0044",
          "source:adr-0045",
          "source:adr-0046",
          "source:adr-0047",
          "source:adr-0048",
          "source:adr-0049",
          "source:adr-0056"
        ],
        "verified_commit": "92db2f3c7ea8d086ccdb1b9c52a2d65c9f81412a"
      },
      "description": "What the portfolio agent remembers, which for now is nothing beyond the tab, and how opt-in memory is designed so that it cannot turn into a profile of you.",
      "lead": {
        "markdown": "Memory is the feature most likely to make an assistant useful and the one most likely to make it creepy. This site starts with none. When memory arrives it is small, opt-in and built so that it can only hold facts about which pages you opened, never a sentence and never a guess about who you are.",
        "text": "Memory is the feature most likely to make an assistant useful and the one most likely to make it creepy. This site starts with none. When memory arrives it is small, opt-in and built so that it can only hold facts about which pages you opened, never a sentence and never a guess about who you are."
      },
      "slug": "memory-personalisation",
      "status": "published",
      "summary": "For now the site remembers no visitor. The conversation lives in your browser tab and is gone when you close it. Memory comes later, off until you turn it on, as a few fields with no text in them.",
      "title": "Memory and personalisation",
      "type": "site",
      "withheld": []
    },
    "site:model-routing-cost-control": {
      "data": {
        "canned": [
          {
            "anchor": "site:model-routing-cost-control#section-which-model-answers",
            "answer": {
              "en": "Answers are written by GPT-5.6 Luna, an OpenAI model. Before a question reaches it, a small classifier, TypeSafe's Jev, reached through Cloudflare, only decides whether the question is about Francesco, which language it is in, and what it is about, which is recorded and changes nothing in the answer. The answering model was chosen by running six models against a test set with a pass mark fixed in advance, and changing it means running that set again.",
              "it": "Le risposte sono scritte da GPT-5.6 Luna, un modello di OpenAI. Prima che una domanda gli arrivi, un piccolo classificatore, Jev di TypeSafe, raggiunto tramite Cloudflare, decide soltanto se la domanda riguarda Francesco, in che lingua è scritta e di cosa parla, un dato che viene registrato e non cambia nulla nella risposta. Il modello che risponde è stato scelto mettendo alla prova sei modelli su un insieme di test con una soglia fissata in anticipo, e cambiarlo significa ripetere quei test."
            },
            "id": "which-model",
            "questions": {
              "en": [
                "Which model powers this chat?",
                "Which AI model do you use?",
                "Are you ChatGPT?"
              ],
              "it": [
                "Che modello usi?",
                "Quale modello di AI c'è dietro questa chat?",
                "Sei ChatGPT?"
              ]
            }
          }
        ],
        "claim_rows": [
          "C14",
          "C15"
        ],
        "derived_from": [
          "docs/deep-dives/05-agent-core.md",
          "docs/deep-dives/11-choosing-the-model.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/deep-dives/16-jev-decider.md",
          "docs/decisions/ADR-0039-corpus-projection-freshness-citation.md",
          "docs/decisions/ADR-0040-routing-tiers-scope-gate.md",
          "docs/decisions/ADR-0041-orchestration-turn-budget.md",
          "docs/decisions/ADR-0043-provider-interface-model-tiers.md",
          "docs/decisions/ADR-0050-budgets-limits-ladder-thresholds.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md",
          "docs/decisions/ADR-0073-residency-processors-cost.md",
          "docs/decisions/ADR-0081-scope-gate-on-jev.md",
          "docs/decisions/ADR-0082-jev-slots-and-processor-route.md",
          "docs/decisions/ADR-0087-request-topic-audience-outcome.md"
        ],
        "sources": [
          "source:adr-0039",
          "source:adr-0040",
          "source:adr-0041",
          "source:adr-0043",
          "source:adr-0050",
          "source:adr-0062",
          "source:adr-0073",
          "source:adr-0081",
          "source:adr-0082",
          "source:adr-0087"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "How the portfolio agent routes a question through rules, a scope gate and one answering model, how that model was chosen, and how spend is capped.",
      "lead": {
        "markdown": "The rule behind the routing is that nothing calls a model for what a rule, a lookup or a click can resolve. So a question passes through three tiers, each more expensive than the last, and it stops at the first one that can deal with it. Only the last tier loads the corpus. The spend of the whole system has a fixed ceiling, and when the money runs out the assistant stops spending rather than getting worse.",
        "text": "The rule behind the routing is that nothing calls a model for what a rule, a lookup or a click can resolve. So a question passes through three tiers, each more expensive than the last, and it stops at the first one that can deal with it. Only the last tier loads the corpus. The spend of the whole system has a fixed ceiling, and when the money runs out the assistant stops spending rather than getting worse."
      },
      "slug": "model-routing-cost-control",
      "status": "published",
      "summary": "A question stops at the cheapest layer that can deal with it. Rules come first, one small classifier second and the answering model last, and the whole agent runs inside a $20 monthly ceiling that the providers enforce.",
      "title": "Model routing and cost control",
      "type": "site",
      "withheld": []
    },
    "site:real-metrics": {
      "data": {
        "claim_rows": [
          "C11",
          "C12",
          "C14",
          "C21"
        ],
        "derived_from": [
          "docs/deep-dives/08-seeing-and-judging.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/deep-dives/16-jev-decider.md",
          "docs/decisions/ADR-0039-corpus-projection-freshness-citation.md",
          "docs/decisions/ADR-0055-threat-model-disclosure-boundary.md",
          "docs/decisions/ADR-0057-metric-sheet-dashboard-phases.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md",
          "docs/decisions/ADR-0081-scope-gate-on-jev.md"
        ],
        "sources": [
          "source:adr-0039",
          "source:adr-0055",
          "source:adr-0057",
          "source:adr-0062",
          "source:adr-0081"
        ],
        "verified_commit": "92db2f3c7ea8d086ccdb1b9c52a2d65c9f81412a"
      },
      "description": "Which metrics the portfolio will publish after launch, the rules every published number follows, and what was measured before any visitor arrived.",
      "lead": {
        "markdown": "A case study with metrics is only worth reading if the metrics are honest about where they came from. This page holds the rules every number on How it works follows, what will be published once there is real traffic, and what was measured before any visitor asked anything. It will change more than any other page here, because it is the one that waits for data.",
        "text": "A case study with metrics is only worth reading if the metrics are honest about where they came from. This page holds the rules every number on How it works follows, what will be published once there is real traffic, and what was measured before any visitor asked anything. It will change more than any other page here, because it is the one that waits for data."
      },
      "slug": "real-metrics",
      "status": "published",
      "summary": "No number on these pages comes from real visitors yet. After launch, published metrics come from the metric sheet with their denominators and the date they were read, and until then every figure is a measurement on test sets written for the purpose.",
      "title": "Real metrics after launch",
      "type": "site",
      "withheld": []
    },
    "site:retrieval-context-engineering": {
      "data": {
        "canned": [
          {
            "anchor": "site:retrieval-context-engineering#section-what-the-assistant-may-say",
            "answer": {
              "en": "No, I'm software: an AI assistant on Francesco's site. I answer only from what he has published here, and every answer cites the page it comes from. If something isn't published, I say so rather than guess. To reach Francesco himself, use the contact form.",
              "it": "No, sono un software: un assistente AI sul sito di Francesco. Rispondo solo in base a ciò che lui ha pubblicato qui, e ogni risposta cita la pagina da cui proviene. Se qualcosa non è pubblicato, lo dico invece di tirare a indovinare. Per contattare Francesco di persona, usa il modulo di contatto."
            },
            "id": "is-it-a-person",
            "questions": {
              "en": [
                "Are you a real person?",
                "Am I talking to a bot?",
                "Are you Francesco?"
              ],
              "it": [
                "Sei una persona vera?",
                "Sto parlando con un bot?",
                "Sei Francesco?"
              ]
            }
          }
        ],
        "claim_rows": [
          "C11"
        ],
        "derived_from": [
          "docs/deep-dives/05-agent-core.md",
          "docs/deep-dives/08-seeing-and-judging.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/decisions/ADR-0030-tool-contracts-classes-results.md",
          "docs/decisions/ADR-0038-retrieval-without-an-index.md",
          "docs/decisions/ADR-0039-corpus-projection-freshness-citation.md",
          "docs/decisions/ADR-0040-routing-tiers-scope-gate.md",
          "docs/decisions/ADR-0042-prompt-architecture-trust-fences.md",
          "docs/decisions/ADR-0043-provider-interface-model-tiers.md",
          "docs/decisions/ADR-0044-context-assembly-history-depth.md",
          "docs/decisions/ADR-0062-answering-model-by-disqualification.md"
        ],
        "sources": [
          "source:adr-0030",
          "source:adr-0038",
          "source:adr-0039",
          "source:adr-0040",
          "source:adr-0042",
          "source:adr-0043",
          "source:adr-0044",
          "source:adr-0062"
        ],
        "verified_commit": "92db2f3c7ea8d086ccdb1b9c52a2d65c9f81412a"
      },
      "description": "Why the portfolio agent has no vector store or search index, how its prompt is layered by trust, and how citations are checked after generation.",
      "lead": {
        "markdown": "The usual answer to \"ground an agent in your content\" is retrieval: index the content, fetch the few passages that look relevant, and hope they were the right ones. This site does not retrieve. The portfolio is small enough to put in the prompt whole, so the assistant reads all of it on every turn, and the engineering moves to what surrounds it: what the prompt holds and in what order, what the model may treat as an instruction, and what happens to a citation after the model writes it.",
        "text": "The usual answer to \"ground an agent in your content\" is retrieval: index the content, fetch the few passages that look relevant, and hope they were the right ones. This site does not retrieve. The portfolio is small enough to put in the prompt whole, so the assistant reads all of it on every turn, and the engineering moves to what surrounds it: what the prompt holds and in what order, what the model may treat as an instruction, and what happens to a citation after the model writes it."
      },
      "slug": "retrieval-context-engineering",
      "status": "published",
      "summary": "The assistant does not search. The published portfolio fits in its prompt, so every answer is written with all of it in view, and every citation is checked against the list of real ids before it reaches you.",
      "title": "Retrieval and context engineering",
      "type": "site",
      "withheld": []
    },
    "site:seo-geo-static-representation": {
      "data": {
        "claim_rows": [
          "C2"
        ],
        "derived_from": [
          "docs/deep-dives/01-content-model.md",
          "docs/deep-dives/02-site-ia-and-seo.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/decisions/ADR-0011-information-architecture-routes-urls.md",
          "docs/decisions/ADR-0012-rendering-caching-strategy.md",
          "docs/decisions/ADR-0013-site-toolchain.md",
          "docs/decisions/ADR-0014-page-projection-and-copy.md",
          "docs/decisions/ADR-0015-structured-data-vocabulary.md",
          "docs/decisions/ADR-0016-ai-crawler-policy-exports.md",
          "docs/decisions/ADR-0017-cv-format-generation.md",
          "docs/decisions/ADR-0019-accessibility-performance-budgets.md",
          "docs/decisions/ADR-0020-phase-1-entry-point-ask-route.md",
          "docs/decisions/ADR-0069-one-worker-site-origin.md",
          "docs/decisions/ADR-0085-edge-adds-nothing.md"
        ],
        "sources": [
          "source:adr-0011",
          "source:adr-0012",
          "source:adr-0013",
          "source:adr-0014",
          "source:adr-0015",
          "source:adr-0016",
          "source:adr-0017",
          "source:adr-0019",
          "source:adr-0020",
          "source:adr-0069",
          "source:adr-0085"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "How the portfolio serves search engines and AI crawlers. Static pages from one artefact, stable URLs, JSON-LD, open crawling and kb.json as the export.",
      "lead": {
        "markdown": "A site with an agent on it still has to work as a site. Search engines, AI crawlers, people with JavaScript off and people who never touch the assistant all read the same pages, and those pages have to be complete, fast, stable and true without any help from a model. So the static site is the foundation and the assistant is added on top, never the other way round.",
        "text": "A site with an agent on it still has to work as a site. Search engines, AI crawlers, people with JavaScript off and people who never touch the assistant all read the same pages, and those pages have to be complete, fast, stable and true without any help from a model. So the static site is the foundation and the assistant is added on top, never the other way round."
      },
      "slug": "seo-geo-static-representation",
      "status": "published",
      "summary": "Every page is static HTML built from the same file the assistant reads, with no JavaScript on content pages beyond a 2 KB script that animates the layout, one structured-data graph per page, and the whole corpus published for any machine that wants it.",
      "title": "SEO/GEO and static representation",
      "type": "site",
      "withheld": []
    },
    "site:tool-calling-ui-control": {
      "data": {
        "canned": [
          {
            "anchor": "site:tool-calling-ui-control#section-seven-tools-in-three-classes",
            "answer": {
              "en": "I answer questions about Francesco's work from what this site publishes, and I cite the page each answer comes from. I can look up facts such as dates and availability, point you to the right page or section, and set up a comparison between projects. I can't navigate for you, change the page or send anything: I propose, and you choose what to open. If you want to get in touch, I can take you to the contact form.",
              "it": "Rispondo a domande sul lavoro di Francesco usando ciò che questo sito pubblica, e cito la pagina da cui viene ogni risposta. Posso cercare fatti come date e disponibilità, indicarti la pagina o la sezione giusta e preparare un confronto tra progetti. Non posso navigare al posto tuo, modificare la pagina o inviare nulla: io propongo, e sei tu a scegliere cosa aprire. Se vuoi metterti in contatto, posso portarti al modulo di contatto."
            },
            "id": "what-the-assistant-can-do",
            "questions": {
              "en": [
                "What can you do?",
                "What can this assistant do?",
                "How can you help me?"
              ],
              "it": [
                "Cosa sai fare?",
                "Cosa può fare questo assistente?",
                "Come mi puoi aiutare?"
              ]
            }
          }
        ],
        "claim_rows": [
          "C8",
          "C9",
          "C10",
          "C16"
        ],
        "derived_from": [
          "docs/deep-dives/04-agent-ui-contract.md",
          "docs/deep-dives/15-disclosure-pages.md",
          "docs/decisions/ADR-0020-phase-1-entry-point-ask-route.md",
          "docs/decisions/ADR-0030-tool-contracts-classes-results.md",
          "docs/decisions/ADR-0031-tool-execution-in-process-mcp.md",
          "docs/decisions/ADR-0032-ui-actions-catalogue-authorisation.md",
          "docs/decisions/ADR-0033-external-class-confirmation-protocol.md",
          "docs/decisions/ADR-0034-turn-wire-transport-frames.md",
          "docs/decisions/ADR-0041-orchestration-turn-budget.md",
          "docs/decisions/ADR-0042-prompt-architecture-trust-fences.md",
          "docs/decisions/ADR-0055-threat-model-disclosure-boundary.md",
          "docs/decisions/ADR-0063-one-contact-backend-no-js-review.md",
          "docs/decisions/ADR-0065-empty-form-message-by-template.md",
          "docs/decisions/ADR-0074-mail-transport-cloudflare-send-email.md"
        ],
        "sources": [
          "source:adr-0020",
          "source:adr-0030",
          "source:adr-0031",
          "source:adr-0032",
          "source:adr-0033",
          "source:adr-0034",
          "source:adr-0041",
          "source:adr-0042",
          "source:adr-0055",
          "source:adr-0063",
          "source:adr-0065",
          "source:adr-0074"
        ],
        "verified_commit": "4e59cca20a2e07b9b6654d506928055c0c3da2fb"
      },
      "description": "The portfolio agent's seven tools, how its UI actions are authorised, and why the model has no tool that sends a message.",
      "lead": {
        "markdown": "An agent that can act on a page is only as safe as the list of things it can do. So the list here is short, every entry is a contract, and the most consequential capabilities are missing on purpose. The model proposes. Code checks what it proposed. You decide what happens.",
        "text": "An agent that can act on a page is only as safe as the list of things it can do. So the list here is short, every entry is a contract, and the most consequential capabilities are missing on purpose. The model proposes. Code checks what it proposed. You decide what happens."
      },
      "slug": "tool-calling-ui-control",
      "status": "published",
      "summary": "The assistant can look facts up and propose where to go next. It cannot navigate, cannot rearrange the page and cannot send a message, and every destination it proposes is checked against the site's routes twice.",
      "title": "Tool calling and UI control",
      "type": "site",
      "withheld": []
    },
    "skill:agent-assisted-delivery": {
      "data": {
        "aliases": [
          "AI-assisted development",
          "coding agents",
          "agent-driven engineering",
          "Claude Code"
        ],
        "category": "agentic-delivery",
        "evidence_count": 6,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Agent-assisted delivery",
        "years": 0.7
      },
      "slug": "agent-assisted-delivery",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:agent-orchestration": {
      "data": {
        "aliases": [
          "multi-agent systems",
          "invocation kernels"
        ],
        "category": "agentic-ai",
        "evidence_count": 3,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Agent orchestration",
        "years": 0.7
      },
      "slug": "agent-orchestration",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:architecture-decision-records": {
      "data": {
        "aliases": [
          "ADRs",
          "design reviews"
        ],
        "category": "ways-of-working",
        "evidence_count": 1,
        "featured": true,
        "last_used": "2026-02",
        "name": "Architecture decision records",
        "years": 0.7
      },
      "slug": "architecture-decision-records",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:aws-serverless": {
      "data": {
        "aliases": [
          "Lambda",
          "Step Functions",
          "DynamoDB"
        ],
        "category": "cloud-and-devops",
        "evidence_count": 2,
        "featured": true,
        "last_used": "2026-02",
        "name": "AWS serverless",
        "years": 3.7
      },
      "slug": "aws-serverless",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:clickhouse": {
      "data": {
        "category": "data",
        "evidence_count": 2,
        "featured": false,
        "last_used": "2026-09-18",
        "name": "ClickHouse",
        "years": 0.7
      },
      "slug": "clickhouse",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:context-engineering": {
      "data": {
        "aliases": [
          "prompt versioning",
          "agent instructions",
          "knowledge for agents"
        ],
        "category": "agentic-delivery",
        "evidence_count": 2,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Context engineering",
        "years": 0.5
      },
      "slug": "context-engineering",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:developer-tooling": {
      "data": {
        "category": "ways-of-working",
        "evidence_count": 3,
        "featured": false,
        "last_used": "2026-09-19",
        "name": "Developer tooling",
        "years": 0.5
      },
      "slug": "developer-tooling",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:embedded-electronics": {
      "data": {
        "category": "other",
        "evidence_count": 1,
        "featured": false,
        "last_used": "2017-08",
        "name": "Embedded electronics",
        "years": 1
      },
      "slug": "embedded-electronics",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:eval-harnesses": {
      "data": {
        "aliases": [
          "LLM evals",
          "prompt regression testing"
        ],
        "category": "ai-reliability-and-cost",
        "evidence_count": 1,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Eval harnesses and regression testing",
        "years": 0.7
      },
      "slug": "eval-harnesses",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:finops-for-ai": {
      "data": {
        "aliases": [
          "AI cost engineering",
          "LLM cost attribution"
        ],
        "category": "ai-reliability-and-cost",
        "evidence_count": 2,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "FinOps for AI",
        "years": 0.7
      },
      "slug": "finops-for-ai",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:go": {
      "data": {
        "category": "backend",
        "evidence_count": 2,
        "featured": false,
        "last_used": "2026-09-19",
        "name": "Go",
        "years": 0.7
      },
      "slug": "go",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:guardrails": {
      "data": {
        "category": "agentic-ai",
        "evidence_count": 3,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Guardrails and policy enforcement",
        "years": 0.7
      },
      "slug": "guardrails",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:java-spring": {
      "data": {
        "aliases": [
          "Java 17",
          "Spring Boot",
          "J2EE"
        ],
        "category": "backend",
        "evidence_count": 1,
        "featured": false,
        "last_used": "2021-04",
        "name": "Java and Spring",
        "years": 3
      },
      "slug": "java-spring",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:knowledge-engineering": {
      "data": {
        "aliases": [
          "provenance",
          "drift detection",
          "LLM wiki pattern"
        ],
        "category": "agentic-ai",
        "evidence_count": 5,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Knowledge engineering for agents",
        "years": 0.2
      },
      "slug": "knowledge-engineering",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:kubernetes": {
      "data": {
        "aliases": [
          "EKS",
          "k3s",
          "Docker"
        ],
        "category": "cloud-and-devops",
        "evidence_count": 1,
        "featured": false,
        "last_used": "2021-04",
        "name": "Kubernetes",
        "years": 3
      },
      "slug": "kubernetes",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:llm-observability": {
      "data": {
        "aliases": [
          "OpenTelemetry gen_ai",
          "LLM tracing"
        ],
        "category": "ai-reliability-and-cost",
        "evidence_count": 5,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "LLM observability and tracing",
        "sources": [
          "source:otel-gen-ai"
        ],
        "years": 0.7
      },
      "slug": "llm-observability",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:mcp-servers": {
      "data": {
        "aliases": [
          "Model Context Protocol"
        ],
        "category": "agentic-ai",
        "evidence_count": 3,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "MCP servers",
        "years": 0.3
      },
      "slug": "mcp-servers",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:model-routing": {
      "data": {
        "aliases": [
          "model tier selection",
          "cost-aware routing"
        ],
        "category": "ai-reliability-and-cost",
        "evidence_count": 1,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Model routing",
        "years": 0.7
      },
      "slug": "model-routing",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:multi-tenant-saas": {
      "data": {
        "aliases": [
          "BYOC",
          "self-hosted distribution"
        ],
        "category": "architecture",
        "evidence_count": 4,
        "featured": false,
        "last_used": "2026-09-19",
        "name": "Multi-tenant SaaS architecture",
        "years": 0.7
      },
      "slug": "multi-tenant-saas",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:product-discovery": {
      "data": {
        "category": "ways-of-working",
        "evidence_count": 1,
        "featured": false,
        "last_used": "2026-07",
        "name": "Product discovery and go-to-market",
        "years": 0.5
      },
      "slug": "product-discovery",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:python-fastapi": {
      "data": {
        "aliases": [
          "Python 3",
          "FastAPI"
        ],
        "category": "backend",
        "evidence_count": 5,
        "featured": true,
        "last_used": "2026-09-19",
        "name": "Python and FastAPI",
        "years": 4.3
      },
      "slug": "python-fastapi",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:swift-swiftui": {
      "data": {
        "category": "frontend",
        "evidence_count": 1,
        "featured": false,
        "last_used": "2026-09-19",
        "name": "Swift and SwiftUI",
        "years": 0.3
      },
      "slug": "swift-swiftui",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:terraform": {
      "data": {
        "aliases": [
          "infrastructure as code"
        ],
        "category": "cloud-and-devops",
        "evidence_count": 3,
        "featured": true,
        "last_used": "2026-09-18",
        "name": "Terraform",
        "years": 1.3
      },
      "slug": "terraform",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "skill:typescript": {
      "data": {
        "category": "backend",
        "evidence_count": 2,
        "featured": false,
        "last_used": "2026-09-19",
        "name": "TypeScript",
        "years": 0.2
      },
      "slug": "typescript",
      "status": "published",
      "type": "skill",
      "withheld": []
    },
    "source:accreta-atlas-repo": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "repository",
        "publisher": "GitHub",
        "url": "https://github.com/francescofioredev/accreta-atlas"
      },
      "slug": "accreta-atlas-repo",
      "status": "published",
      "title": "accreta-atlas",
      "type": "source",
      "withheld": []
    },
    "source:accreta-npm": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "package",
        "publisher": "npm",
        "url": "https://www.npmjs.com/package/accreta"
      },
      "slug": "accreta-npm",
      "status": "published",
      "title": "accreta on npm",
      "type": "source",
      "withheld": []
    },
    "source:accreta-repo": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "repository",
        "publisher": "GitHub",
        "url": "https://github.com/francescofioredev/accreta"
      },
      "slug": "accreta-repo",
      "status": "published",
      "title": "accreta",
      "type": "source",
      "withheld": []
    },
    "source:adr-0001": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0001",
      "status": "published",
      "title": "ADR-0001: Docs-first repo with logical components before stack",
      "type": "source",
      "withheld": []
    },
    "source:adr-0002": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0002",
      "status": "published",
      "title": "ADR-0002: Source format, layout and the compiled artefact as the only contract",
      "type": "source",
      "withheld": []
    },
    "source:adr-0003": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0003",
      "status": "published",
      "title": "ADR-0003: Knowledge-base toolchain",
      "type": "source",
      "withheld": []
    },
    "source:adr-0004": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0004",
      "status": "published",
      "title": "ADR-0004: Entity catalogue, relations and evidence",
      "type": "source",
      "withheld": []
    },
    "source:adr-0005": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0005",
      "status": "published",
      "title": "ADR-0005: Visibility tiers, private overlay and leak testing",
      "type": "source",
      "withheld": []
    },
    "source:adr-0006": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0006",
      "status": "published",
      "title": "ADR-0006: Ids, anchors, slugs and redirects",
      "type": "source",
      "withheld": []
    },
    "source:adr-0007": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0007",
      "status": "published",
      "title": "ADR-0007: Validity, staleness and invalidation",
      "type": "source",
      "withheld": []
    },
    "source:adr-0008": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0008",
      "status": "published",
      "title": "ADR-0008: English-only content",
      "type": "source",
      "withheld": []
    },
    "source:adr-0009": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0009",
      "status": "published",
      "title": "ADR-0009: Editorial loop — site architecture sync, unknown questions, style guide",
      "type": "source",
      "withheld": []
    },
    "source:adr-0010": {
      "data": {
        "date": "2026-09-18",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0010",
      "status": "published",
      "title": "ADR-0010: Naming third parties in public content",
      "type": "source",
      "withheld": []
    },
    "source:adr-0011": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0011",
      "status": "published",
      "title": "ADR-0011: Information architecture, routes and the URL grammar",
      "type": "source",
      "withheld": []
    },
    "source:adr-0012": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0012",
      "status": "published",
      "title": "ADR-0012: Rendering and caching strategy",
      "type": "source",
      "withheld": []
    },
    "source:adr-0013": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0013",
      "status": "published",
      "title": "ADR-0013: Site toolchain",
      "type": "source",
      "withheld": []
    },
    "source:adr-0014": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0014",
      "status": "published",
      "title": "ADR-0014: Page projection from `kb.json`, and the copy it implies",
      "type": "source",
      "withheld": []
    },
    "source:adr-0015": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0015",
      "status": "published",
      "title": "ADR-0015: Structured-data vocabulary",
      "type": "source",
      "withheld": []
    },
    "source:adr-0016": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0016",
      "status": "published",
      "title": "ADR-0016: AI-crawler policy and machine-readable exports",
      "type": "source",
      "withheld": []
    },
    "source:adr-0017": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0017",
      "status": "published",
      "title": "ADR-0017: CV format and generation",
      "type": "source",
      "withheld": []
    },
    "source:adr-0018": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0018",
      "status": "published",
      "title": "ADR-0018: Progressive layout slots and the home initial state",
      "type": "source",
      "withheld": []
    },
    "source:adr-0019": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0019",
      "status": "published",
      "title": "ADR-0019: Accessibility and performance budgets, and the design constraints they set",
      "type": "source",
      "withheld": []
    },
    "source:adr-0020": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0020",
      "status": "published",
      "title": "ADR-0020: The Phase-1 presence, and the route where the agent runs",
      "type": "source",
      "withheld": []
    },
    "source:adr-0021": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0021",
      "status": "published",
      "title": "ADR-0021: The form of the presence, its state grammar, and how it moves",
      "type": "source",
      "withheld": []
    },
    "source:adr-0022": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0022",
      "status": "published",
      "title": "ADR-0022: Who owns the presence machine, and what survives a navigation",
      "type": "source",
      "withheld": []
    },
    "source:adr-0023": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0023",
      "status": "published",
      "title": "ADR-0023: The attention budget — when the companion may speak, and how it learns to stop",
      "type": "source",
      "withheld": []
    },
    "source:adr-0024": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0024",
      "status": "published",
      "title": "ADR-0024: Where suggestions come from, and what the rail does with nothing to say",
      "type": "source",
      "withheld": []
    },
    "source:adr-0025": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0025",
      "status": "published",
      "title": "ADR-0025: The context radar — where it exists, what triggers it, what it offers",
      "type": "source",
      "withheld": []
    },
    "source:adr-0026": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0026",
      "status": "published",
      "title": "ADR-0026: The dock — container, focus, dismissal and the mobile sheet",
      "type": "source",
      "withheld": []
    },
    "source:adr-0027": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0027",
      "status": "published",
      "title": "ADR-0027: What a screen reader hears",
      "type": "source",
      "withheld": []
    },
    "source:adr-0028": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0028",
      "status": "published",
      "title": "ADR-0028: How the 60 KB is spent — island runtime, state machine and apportionment",
      "type": "source",
      "withheld": []
    },
    "source:adr-0029": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0029",
      "status": "published",
      "title": "ADR-0029: Amendments to the layout contract required by the companion",
      "type": "source",
      "withheld": []
    },
    "source:adr-0030": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0030",
      "status": "published",
      "title": "ADR-0030: Tool contracts — one source, three classes, and what a result carries",
      "type": "source",
      "withheld": []
    },
    "source:adr-0031": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0031",
      "status": "published",
      "title": "ADR-0031: Where tools run, and what an MCP surface would be for",
      "type": "source",
      "withheld": []
    },
    "source:adr-0032": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0032",
      "status": "published",
      "title": "ADR-0032: The UI action — two kinds, and the click that authorises the destructive one",
      "type": "source",
      "withheld": []
    },
    "source:adr-0033": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0033",
      "status": "published",
      "title": "ADR-0033: The external class — the model proposes, the visitor disposes, the server executes",
      "type": "source",
      "withheld": []
    },
    "source:adr-0034": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0034",
      "status": "published",
      "title": "ADR-0034: The wire — one POST, NDJSON frames, three timeouts",
      "type": "source",
      "withheld": []
    },
    "source:adr-0035": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0035",
      "status": "published",
      "title": "ADR-0035: What lives where, and what survives a navigation",
      "type": "source",
      "withheld": []
    },
    "source:adr-0036": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0036",
      "status": "published",
      "title": "ADR-0036: One key, one object — client storage and the context payload",
      "type": "source",
      "withheld": []
    },
    "source:adr-0037": {
      "data": {
        "date": "2026-09-19",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0037",
      "status": "published",
      "title": "ADR-0037: The client event vocabulary",
      "type": "source",
      "withheld": []
    },
    "source:adr-0038": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0038",
      "status": "published",
      "title": "ADR-0038: Retrieval without an index — the corpus is the context",
      "type": "source",
      "withheld": []
    },
    "source:adr-0039": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0039",
      "status": "published",
      "title": "ADR-0039: The corpus projection — build, freshness, citation and what is cached",
      "type": "source",
      "withheld": []
    },
    "source:adr-0040": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0040",
      "status": "published",
      "title": "ADR-0040: Three tiers, one gate — where a request stops being cheap",
      "type": "source",
      "withheld": []
    },
    "source:adr-0041": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0041",
      "status": "published",
      "title": "ADR-0041: One agent, one bounded loop — the turn's budget and how it degrades",
      "type": "source",
      "withheld": []
    },
    "source:adr-0042": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0042",
      "status": "published",
      "title": "ADR-0042: The prompt — four layers, three trust levels, and an answer that cannot contain a link",
      "type": "source",
      "withheld": []
    },
    "source:adr-0043": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0043",
      "status": "published",
      "title": "ADR-0043: The provider port, and the models behind it",
      "type": "source",
      "withheld": []
    },
    "source:adr-0044": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0044",
      "status": "published",
      "title": "ADR-0044: What a turn carries besides the corpus — thread, focus, depth and the facts projection",
      "type": "source",
      "withheld": []
    },
    "source:adr-0045": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0045",
      "status": "published",
      "title": "ADR-0045: The first identifier that outlives a tab, and the first server state",
      "type": "source",
      "withheld": []
    },
    "source:adr-0046": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0046",
      "status": "published",
      "title": "ADR-0046: A record of what the visitor did, and no record of what we concluded",
      "type": "source",
      "withheld": []
    },
    "source:adr-0047": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0047",
      "status": "published",
      "title": "ADR-0047: One writer, no model, and a delete that leaves nothing behind",
      "type": "source",
      "withheld": []
    },
    "source:adr-0048": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0048",
      "status": "published",
      "title": "ADR-0048: Asked once, in the open, by something the visitor already opened",
      "type": "source",
      "withheld": []
    },
    "source:adr-0049": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0049",
      "status": "published",
      "title": "ADR-0049: What memory is allowed to move, and the rule that stops it moving anything the visitor is reading",
      "type": "source",
      "withheld": []
    },
    "source:adr-0050": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0050",
      "status": "published",
      "title": "ADR-0050: Twenty dollars a month — the budgets, the limits, and the numbers under the ladder",
      "type": "source",
      "withheld": []
    },
    "source:adr-0051": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0051",
      "status": "published",
      "title": "ADR-0051: The one-hour cache — bought for the visitor who reads before asking again",
      "type": "source",
      "withheld": []
    },
    "source:adr-0052": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0052",
      "status": "published",
      "title": "ADR-0052: Abuse without a CAPTCHA — bots, the shared link, and the four alerts",
      "type": "source",
      "withheld": []
    },
    "source:adr-0053": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0053",
      "status": "published",
      "title": "ADR-0053: Four tiers, no banner — consent as an input, and a Phase 1 that needs none",
      "type": "source",
      "withheld": []
    },
    "source:adr-0054": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0054",
      "status": "published",
      "title": "ADR-0054: Eight surfaces, one rule — retention, redaction, and no visitor text at rest",
      "type": "source",
      "withheld": []
    },
    "source:adr-0055": {
      "data": {
        "date": "2026-09-20",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0055",
      "status": "published",
      "title": "ADR-0055: The threat model in one place — no moderation layer, and a case study that may not overclaim",
      "type": "source",
      "withheld": []
    },
    "source:adr-0056": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0056",
      "status": "published",
      "title": "ADR-0056: The turn trace — one record, no sentence, and a gap that is a bucket",
      "type": "source",
      "withheld": []
    },
    "source:adr-0057": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0057",
      "status": "published",
      "title": "ADR-0057: The metric sheet — what §21 can be read from, what cannot, and no dashboard until Phase 4",
      "type": "source",
      "withheld": []
    },
    "source:adr-0058": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0058",
      "status": "published",
      "title": "ADR-0058: The golden set — fifty-one cases, authored, and keyed to `ids.lock`",
      "type": "source",
      "withheld": []
    },
    "source:adr-0059": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0059",
      "status": "published",
      "title": "ADR-0059: Two layers of grading — asserts first, and a judge that is a gate rather than a score",
      "type": "source",
      "withheld": []
    },
    "source:adr-0060": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0060",
      "status": "published",
      "title": "ADR-0060: The gates — what re-runs the set, what blocks a deploy, and what a run costs",
      "type": "source",
      "withheld": []
    },
    "source:adr-0061": {
      "data": {
        "date": "2026-09-22",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0061",
      "status": "published",
      "title": "ADR-0061: The twenty-fifth event — a feedback signal with no sentence in it, and a monthly read",
      "type": "source",
      "withheld": []
    },
    "source:adr-0062": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0062",
      "status": "published",
      "title": "ADR-0062: The answering model — GPT-5.6 Luna, chosen by disqualification and one owner's call",
      "type": "source",
      "withheld": []
    },
    "source:adr-0063": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0063",
      "status": "published",
      "title": "ADR-0063: One contact backend — a no-JavaScript review step in front of the same `/confirm`",
      "type": "source",
      "withheld": []
    },
    "source:adr-0064": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0064",
      "status": "published",
      "title": "ADR-0064: One field catalogue for both phases, offered only when asked",
      "type": "source",
      "withheld": []
    },
    "source:adr-0065": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0065",
      "status": "published",
      "title": "ADR-0065: The form opens empty, and the message is a template",
      "type": "source",
      "withheld": []
    },
    "source:adr-0066": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0066",
      "status": "published",
      "title": "ADR-0066: Delivery — one pinned mailbox, plain text, and a transport deep-dive 10 chooses to a spec",
      "type": "source",
      "withheld": []
    },
    "source:adr-0067": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0067",
      "status": "published",
      "title": "ADR-0067: The contact row — conversion, qualification and lead origin with no value in them",
      "type": "source",
      "withheld": []
    },
    "source:adr-0068": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0068",
      "status": "published",
      "title": "ADR-0068: Domain francescofiore.dev on Cloudflare Registrar",
      "type": "source",
      "withheld": []
    },
    "source:adr-0069": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0069",
      "status": "published",
      "title": "ADR-0069: One Worker on the site's origin — static assets, agent and contact in one deploy",
      "type": "source",
      "withheld": []
    },
    "source:adr-0070": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0070",
      "status": "published",
      "title": "ADR-0070: Three stores — a ledger object, memory as objects, the trace in SQL",
      "type": "source",
      "withheld": []
    },
    "source:adr-0071": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0071",
      "status": "published",
      "title": "ADR-0071: `/ask` without a query string — a POST, a 303, and the question in the fragment",
      "type": "source",
      "withheld": []
    },
    "source:adr-0072": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0072",
      "status": "published",
      "title": "ADR-0072: Terraform for everything with a provider, one pipeline, one preview slot",
      "type": "source",
      "withheld": []
    },
    "source:adr-0073": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0073",
      "status": "published",
      "title": "ADR-0073: EU at rest, processed at the edge — the processors, what each keeps, and $6 a month",
      "type": "source",
      "withheld": []
    },
    "source:adr-0074": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0074",
      "status": "published",
      "title": "ADR-0074: The mail transport — Cloudflare's `send_email` binding, locked to one address",
      "type": "source",
      "withheld": []
    },
    "source:adr-0075": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0075",
      "status": "published",
      "title": "ADR-0075: The repository layout — deployables in `apps/`, libraries in `packages/`",
      "type": "source",
      "withheld": []
    },
    "source:adr-0076": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0076",
      "status": "published",
      "title": "ADR-0076: Four packages and the import graph between them",
      "type": "source",
      "withheld": []
    },
    "source:adr-0077": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0077",
      "status": "published",
      "title": "ADR-0077: The workspace toolchain — pnpm 12, Node 24, TypeScript 6, packages as source",
      "type": "source",
      "withheld": []
    },
    "source:adr-0078": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0078",
      "status": "published",
      "title": "ADR-0078: Boundary enforcement — install, cruise, guard, and a build without `content/`",
      "type": "source",
      "withheld": []
    },
    "source:adr-0079": {
      "data": {
        "date": "2026-09-23",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0079",
      "status": "published",
      "title": "ADR-0079: TypeScript owns the prompt, the projection and the frame schema; Python reads artefacts",
      "type": "source",
      "withheld": []
    },
    "source:adr-0080": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0080",
      "status": "published",
      "title": "ADR-0080: Visual identity \"Workspace\" — families, colour roles, scales, motion and the mark",
      "type": "source",
      "withheld": []
    },
    "source:adr-0081": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0081",
      "status": "published",
      "title": "ADR-0081: The scope gate knows his names and runs on Jev",
      "type": "source",
      "withheld": []
    },
    "source:adr-0082": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0082",
      "status": "published",
      "title": "ADR-0082: Jev's other slots, and the route it takes to reach TypeSafe",
      "type": "source",
      "withheld": []
    },
    "source:adr-0083": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0083",
      "status": "published",
      "title": "ADR-0083: `/privacy` is an Article 13 notice written in-house, with no cookie policy beside it",
      "type": "source",
      "withheld": []
    },
    "source:adr-0084": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0084",
      "status": "published",
      "title": "ADR-0084: One data file and a drift check that blocks — keeping `/privacy` and `/how-it-works` true",
      "type": "source",
      "withheld": []
    },
    "source:adr-0085": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0085",
      "status": "published",
      "title": "ADR-0085: The edge adds nothing — no cookie, no script, no rewrite",
      "type": "source",
      "withheld": []
    },
    "source:adr-0086": {
      "data": {
        "date": "2026-09-24",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0086",
      "status": "published",
      "title": "ADR-0086: Page counts from Cloudflare's own analytics, read daily, kept as totals",
      "type": "source",
      "withheld": []
    },
    "source:adr-0087": {
      "data": {
        "date": "2026-09-25",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0087",
      "status": "published",
      "title": "ADR-0087: What a question is about, who asked it, and how it ended",
      "type": "source",
      "withheld": []
    },
    "source:adr-0088": {
      "data": {
        "date": "2026-09-27",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0088",
      "status": "published",
      "title": "ADR-0088: Visual identity \"Cobalt islands\" — families, colour, islands, the agent wash and motion",
      "type": "source",
      "withheld": []
    },
    "source:adr-0089": {
      "data": {
        "date": "2026-09-27",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0089",
      "status": "published",
      "title": "ADR-0089: Key figures, images and generated diagrams in the content model",
      "type": "source",
      "withheld": []
    },
    "source:adr-0090": {
      "data": {
        "date": "2026-09-27",
        "independent": false,
        "inspectable": false,
        "kind": "adr"
      },
      "slug": "adr-0090",
      "status": "published",
      "title": "ADR-0090: No link into a private repository",
      "type": "source",
      "withheld": []
    },
    "source:agentforge-repo": {
      "data": {
        "independent": false,
        "inspectable": false,
        "kind": "repository",
        "publisher": "GitHub"
      },
      "slug": "agentforge-repo",
      "status": "published",
      "title": "AgentForge",
      "type": "source",
      "withheld": []
    },
    "source:claude-account-switcher-repo": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "repository",
        "publisher": "GitHub",
        "url": "https://github.com/francescofioredev/claude-account-switcher"
      },
      "slug": "claude-account-switcher-repo",
      "status": "published",
      "title": "claude-account-switcher",
      "type": "source",
      "withheld": []
    },
    "source:coding-agent-sync-repo": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "repository",
        "publisher": "GitHub",
        "url": "https://github.com/francescofioredev/coding-agent-sync"
      },
      "slug": "coding-agent-sync-repo",
      "status": "published",
      "title": "coding-agent-sync",
      "type": "source",
      "withheld": []
    },
    "source:disk-reclaim-repo": {
      "data": {
        "independent": false,
        "inspectable": false,
        "kind": "repository",
        "publisher": "GitHub"
      },
      "slug": "disk-reclaim-repo",
      "status": "published",
      "title": "disk-reclaim",
      "type": "source",
      "withheld": []
    },
    "source:focus-spec": {
      "data": {
        "independent": true,
        "inspectable": true,
        "kind": "standard",
        "publisher": "FinOps Foundation",
        "url": "https://focus.finops.org"
      },
      "slug": "focus-spec",
      "status": "published",
      "title": "FinOps Open Cost and Usage Specification",
      "type": "source",
      "withheld": []
    },
    "source:github-profile": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "profile",
        "publisher": "GitHub",
        "url": "https://github.com/francescofioredev"
      },
      "slug": "github-profile",
      "status": "published",
      "title": "Francesco Fiore on GitHub",
      "type": "source",
      "withheld": []
    },
    "source:linkedin-profile": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "profile",
        "publisher": "LinkedIn",
        "url": "https://www.linkedin.com/in/francesco-fiore-902360138/"
      },
      "slug": "linkedin-profile",
      "status": "published",
      "title": "Francesco Fiore on LinkedIn",
      "type": "source",
      "withheld": []
    },
    "source:otel-gen-ai": {
      "data": {
        "independent": true,
        "inspectable": true,
        "kind": "standard",
        "publisher": "OpenTelemetry",
        "url": "https://opentelemetry.io/docs/specs/semconv/gen-ai/"
      },
      "slug": "otel-gen-ai",
      "status": "published",
      "title": "OpenTelemetry semantic conventions for generative AI",
      "type": "source",
      "withheld": []
    },
    "source:praxis-repo": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "repository",
        "publisher": "GitHub",
        "url": "https://github.com/praxis-os/praxis"
      },
      "slug": "praxis-repo",
      "status": "published",
      "title": "praxis",
      "type": "source",
      "withheld": []
    },
    "source:radicas-site": {
      "data": {
        "independent": false,
        "inspectable": true,
        "kind": "product",
        "publisher": "Radicas",
        "url": "https://www.radicas.ai"
      },
      "slug": "radicas-site",
      "status": "published",
      "title": "Radicas",
      "type": "source",
      "withheld": []
    },
    "style:guide": {
      "data": {
        "agent_notes": [
          "Refer to Francesco by name or as \"he\". The agent is not Francesco and never writes as him.",
          "Answer the question that was asked, then stop. No preamble, no closing offer of more help.",
          "Prefer the concrete case to the general statement. Name the project, the decision or the result.",
          "No praise of Francesco. State what he did and cite it; let the visitor judge.",
          "Quote the fixed strings below verbatim. Never paraphrase them."
        ],
        "banned_phrases": [
          "passionate",
          "rockstar",
          "ninja",
          "guru",
          "10x engineer",
          "visionary",
          "thought leader",
          "results-driven",
          "detail-oriented",
          "self-starter",
          "proven track record",
          "world-class",
          "best-in-class",
          "cutting-edge",
          "state-of-the-art",
          "unparalleled",
          "game-changer",
          "game-changing",
          "revolutionary",
          "next-generation",
          "blazing fast",
          "leverage",
          "leveraging",
          "synergy",
          "seamless",
          "seamlessly",
          "empower",
          "supercharge",
          "unlock the power",
          "think outside the box",
          "holistic",
          "innovative",
          "disruptive",
          "delve",
          "tapestry",
          "testament to",
          "in today's fast-paced",
          "it's worth noting"
        ],
        "fixed_strings": {
          "absent": {
            "en": "Nothing on this site covers {topic}.",
            "it": "Questo sito non contiene nulla su {topic}."
          },
          "as_of": {
            "en": "As of {month YYYY}.",
            "it": "Aggiornato a {month YYYY}."
          },
          "stale": {
            "en": "Last confirmed {month YYYY}; not reconfirmed since.",
            "it": "Ultima conferma a {month YYYY}; nessuna conferma successiva."
          },
          "withheld": {
            "en": "{Topic} is not public — {reason}.",
            "it": "{Topic}: informazione non pubblica — {reason}."
          }
        },
        "private_repositories": [
          "https://github.com/francescofioredev/agentic-portfolio",
          "https://github.com/francescofioredev/disk-reclaim",
          "https://github.com/francescofioredev/agentic-infra-platform"
        ],
        "tone": [
          "Direct and concrete. No generic formulas.",
          "Technically rigorous, and readable by someone who is not a specialist.",
          "Start from the problem, the constraints and the trade-offs, then the result.",
          "Critical of unnecessary complexity.",
          "Pragmatic about architectures, models and tools.",
          "Tie a technical decision to its product or business effect when there is one.",
          "Show ideas through real examples, never through self-description.",
          "No claim without a source on the site. A number carries its evidence or does not appear."
        ]
      },
      "slug": "guide",
      "status": "published",
      "type": "style",
      "withheld": []
    },
    "topic:agentic-ai": {
      "data": {},
      "description": "Francesco's work on agentic AI: orchestration runtimes, agent-maintained knowledge bases, guardrails and AI cost engineering.",
      "lead": {
        "markdown": "The thread running through most of the recent work: agents that can be governed, audited and paid for, rather than demos. It shows up as an orchestration runtime with the guardrails in the kernel, as knowledge bases an agent maintains with provenance, and as measuring what an AI feature actually costs.",
        "text": "The thread running through most of the recent work: agents that can be governed, audited and paid for, rather than demos. It shows up as an orchestration runtime with the guardrails in the kernel, as knowledge bases an agent maintains with provenance, and as measuring what an AI feature actually costs."
      },
      "slug": "agentic-ai",
      "status": "published",
      "summary": "Building LLM systems that survive production — orchestration, grounding, guardrails, evaluation and the cost of running them.",
      "title": "Agentic AI",
      "type": "topic",
      "withheld": []
    }
  },
  "relations": [
    {
      "from": "experience:founder-in-residence-reef",
      "to": "org:reef-by-vento",
      "type": "employer"
    },
    {
      "from": "experience:founder-in-residence-reef",
      "note": "problem discovery through to go-to-market",
      "to": "skill:product-discovery",
      "type": "skills"
    },
    {
      "from": "experience:founder-in-residence-reef",
      "to": "source:linkedin-profile",
      "type": "sources"
    },
    {
      "from": "experience:founder-radicas",
      "to": "org:radicas",
      "type": "employer"
    },
    {
      "from": "experience:founder-radicas",
      "note": "the delivery approach behind the product",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "note": "an eval harness gates every release",
      "to": "skill:eval-harnesses",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "note": "the product itself",
      "to": "skill:finops-for-ai",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "note": "OpenTelemetry gen_ai spans priced and reconciled",
      "to": "skill:llm-observability",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "note": "model tier selected per request against a cost ceiling",
      "to": "skill:model-routing",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "to": "skill:multi-tenant-saas",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "to": "skill:python-fastapi",
      "type": "skills"
    },
    {
      "from": "experience:founder-radicas",
      "to": "source:radicas-site",
      "type": "sources"
    },
    {
      "from": "experience:salento-racing-team",
      "to": "org:salento-racing",
      "type": "employer"
    },
    {
      "from": "experience:salento-racing-team",
      "note": "the car's electrical system",
      "to": "skill:embedded-electronics",
      "type": "skills"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "to": "org:itv",
      "type": "client"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "to": "org:fincons-group",
      "type": "employer"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "note": "decisions formalised as ADRs and design docs",
      "to": "skill:architecture-decision-records",
      "type": "skills"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "note": "Lambda and DynamoDB automation",
      "to": "skill:aws-serverless",
      "type": "skills"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "note": "the services around the media orchestration platform",
      "to": "skill:python-fastapi",
      "type": "skills"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "note": "Terraform-backed CI/CD",
      "to": "skill:terraform",
      "type": "skills"
    },
    {
      "from": "experience:senior-swe-fincons-itv",
      "to": "source:linkedin-profile",
      "type": "sources"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "to": "org:enel-green-power",
      "type": "client"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "to": "org:exprivia",
      "type": "employer"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "to": "skill:aws-serverless",
      "type": "skills"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "note": "Java 11, J2EE, Hibernate and JPA",
      "to": "skill:java-spring",
      "type": "skills"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "to": "skill:kubernetes",
      "type": "skills"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "note": "Python 3 backend services",
      "to": "skill:python-fastapi",
      "type": "skills"
    },
    {
      "from": "experience:swe-exprivia-enel",
      "to": "source:linkedin-profile",
      "type": "sources"
    },
    {
      "from": "page:home",
      "to": "principle:let-the-system-do-the-heavy-lifting#what-the-structure-actually-is",
      "type": "suggested_paths"
    },
    {
      "from": "page:home",
      "to": "project:accreta#decision-compile-not-retrieve",
      "type": "suggested_paths"
    },
    {
      "from": "page:home",
      "to": "project:praxis#decision-guardrails-in-kernel",
      "type": "suggested_paths"
    },
    {
      "from": "page:home",
      "to": "project:radicas#problem",
      "type": "suggested_paths"
    },
    {
      "from": "person:francesco-fiore",
      "to": "source:github-profile",
      "type": "sources"
    },
    {
      "from": "person:francesco-fiore",
      "to": "source:linkedin-profile",
      "type": "sources"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "project:accreta#decision-compile-not-retrieve",
      "type": "examples"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "project:accreta#decision-mcp-beside-cli",
      "type": "examples"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "project:accreta-atlas",
      "type": "examples"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "project:claude-account-switcher#claim-built-in-a-day",
      "type": "examples"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "project:coding-agent-sync",
      "type": "examples"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "skill:context-engineering",
      "type": "skills"
    },
    {
      "from": "principle:let-the-system-do-the-heavy-lifting",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:accreta",
      "note": "built end to end through coding agents, six phases in about a month",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "project:accreta",
      "note": "the constitution — the agent's operating rules, versioned as a template",
      "to": "skill:context-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta",
      "note": "the provenance and drift model",
      "to": "skill:knowledge-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta",
      "note": "ships an MCP server beside the CLI",
      "to": "skill:mcp-servers",
      "type": "skills"
    },
    {
      "from": "project:accreta",
      "to": "skill:typescript",
      "type": "skills"
    },
    {
      "from": "project:accreta",
      "to": "source:accreta-npm",
      "type": "sources"
    },
    {
      "from": "project:accreta",
      "to": "source:accreta-repo",
      "type": "sources"
    },
    {
      "from": "project:accreta",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:accreta#claim-published-npm",
      "to": "source:accreta-atlas-repo",
      "type": "evidence"
    },
    {
      "from": "project:accreta#claim-published-npm",
      "to": "source:accreta-npm",
      "type": "evidence"
    },
    {
      "from": "project:accreta#claim-six-phases-in-a-month",
      "to": "source:accreta-npm",
      "type": "evidence"
    },
    {
      "from": "project:accreta#claim-six-phases-in-a-month",
      "to": "source:accreta-repo",
      "type": "evidence"
    },
    {
      "from": "project:accreta#decision-compile-not-retrieve",
      "to": "skill:knowledge-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta#decision-drift-detection",
      "to": "skill:knowledge-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta#decision-mcp-beside-cli",
      "to": "skill:mcp-servers",
      "type": "skills"
    },
    {
      "from": "project:accreta#decision-provenance-to-revision",
      "to": "skill:knowledge-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta-atlas",
      "note": "drift detection running in CI as a real assertion",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "project:accreta-atlas",
      "note": "a corpus large enough to be a real test",
      "to": "skill:knowledge-engineering",
      "type": "skills"
    },
    {
      "from": "project:accreta-atlas",
      "to": "skill:typescript",
      "type": "skills"
    },
    {
      "from": "project:accreta-atlas",
      "to": "source:accreta-atlas-repo",
      "type": "sources"
    },
    {
      "from": "project:accreta-atlas",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:accreta-atlas#claim-drift-goes-red",
      "to": "source:accreta-atlas-repo",
      "type": "evidence"
    },
    {
      "from": "project:accreta-atlas#claim-rfc-corpus",
      "to": "source:accreta-atlas-repo",
      "type": "evidence"
    },
    {
      "from": "project:agentforge",
      "to": "skill:agent-orchestration",
      "type": "skills"
    },
    {
      "from": "project:agentforge",
      "to": "skill:guardrails",
      "type": "skills"
    },
    {
      "from": "project:agentforge",
      "to": "skill:multi-tenant-saas",
      "type": "skills"
    },
    {
      "from": "project:agentforge",
      "to": "source:agentforge-repo",
      "type": "sources"
    },
    {
      "from": "project:agentforge",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:agentforge#claim-design-only",
      "to": "source:agentforge-repo",
      "type": "evidence"
    },
    {
      "from": "project:agentforge#claim-six-guardrail-layers",
      "to": "source:agentforge-repo",
      "type": "evidence"
    },
    {
      "from": "project:claude-account-switcher",
      "note": "tooling for running coding agents across projects",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "project:claude-account-switcher",
      "to": "skill:developer-tooling",
      "type": "skills"
    },
    {
      "from": "project:claude-account-switcher",
      "to": "source:claude-account-switcher-repo",
      "type": "sources"
    },
    {
      "from": "project:claude-account-switcher#claim-built-in-a-day",
      "to": "source:claude-account-switcher-repo",
      "type": "evidence"
    },
    {
      "from": "project:claude-account-switcher#claim-nothing-patched",
      "to": "source:claude-account-switcher-repo",
      "type": "evidence"
    },
    {
      "from": "project:coding-agent-sync",
      "note": "the manifest that keeps every agent's instructions in step",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "project:coding-agent-sync",
      "note": "one source of truth for what every coding agent is told",
      "to": "skill:context-engineering",
      "type": "skills"
    },
    {
      "from": "project:coding-agent-sync",
      "to": "skill:developer-tooling",
      "type": "skills"
    },
    {
      "from": "project:coding-agent-sync",
      "note": "written in Python",
      "to": "skill:python-fastapi",
      "type": "skills"
    },
    {
      "from": "project:coding-agent-sync",
      "to": "source:coding-agent-sync-repo",
      "type": "sources"
    },
    {
      "from": "project:coding-agent-sync",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:coding-agent-sync#claim-doctor-fails-ci",
      "to": "source:coding-agent-sync-repo",
      "type": "evidence"
    },
    {
      "from": "project:coding-agent-sync#claim-one-manifest",
      "to": "source:coding-agent-sync-repo",
      "type": "evidence"
    },
    {
      "from": "project:disk-reclaim",
      "to": "skill:developer-tooling",
      "type": "skills"
    },
    {
      "from": "project:disk-reclaim",
      "note": "the same core exposed to an agent",
      "to": "skill:mcp-servers",
      "type": "skills"
    },
    {
      "from": "project:disk-reclaim",
      "to": "skill:swift-swiftui",
      "type": "skills"
    },
    {
      "from": "project:disk-reclaim",
      "to": "source:disk-reclaim-repo",
      "type": "sources"
    },
    {
      "from": "project:disk-reclaim#claim-manual-reclaim",
      "to": "source:disk-reclaim-repo",
      "type": "evidence"
    },
    {
      "from": "project:disk-reclaim#claim-three-surfaces",
      "to": "source:disk-reclaim-repo",
      "type": "evidence"
    },
    {
      "from": "project:praxis",
      "note": "the invocation kernel",
      "to": "skill:agent-orchestration",
      "type": "skills"
    },
    {
      "from": "project:praxis",
      "to": "skill:go",
      "type": "skills"
    },
    {
      "from": "project:praxis",
      "note": "policy hooks and filter chains at every security-sensitive boundary",
      "to": "skill:guardrails",
      "type": "skills"
    },
    {
      "from": "project:praxis",
      "note": "OpenTelemetry is mandatory, not optional",
      "to": "skill:llm-observability",
      "type": "skills"
    },
    {
      "from": "project:praxis",
      "to": "source:praxis-repo",
      "type": "sources"
    },
    {
      "from": "project:praxis",
      "to": "topic:agentic-ai",
      "type": "topics"
    },
    {
      "from": "project:praxis#claim-apache-licence",
      "to": "source:praxis-repo",
      "type": "evidence"
    },
    {
      "from": "project:praxis#claim-four-budget-dimensions",
      "to": "source:praxis-repo",
      "type": "evidence"
    },
    {
      "from": "project:praxis#claim-mandatory-telemetry",
      "to": "source:praxis-repo",
      "type": "evidence"
    },
    {
      "from": "project:praxis#decision-guardrails-in-kernel",
      "to": "skill:guardrails",
      "type": "skills"
    },
    {
      "from": "project:praxis#decision-mandatory-telemetry",
      "to": "skill:llm-observability",
      "type": "skills"
    },
    {
      "from": "project:praxis#decision-provider-agnostic",
      "to": "skill:agent-orchestration",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "to": "org:reef-by-vento",
      "type": "org"
    },
    {
      "from": "project:radicas",
      "note": "problem to first users in a five-month programme, around thirty ADRs behind it",
      "to": "skill:agent-assisted-delivery",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "span and cost store",
      "to": "skill:clickhouse",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "the product itself",
      "to": "skill:finops-for-ai",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "OpenTelemetry collector",
      "to": "skill:go",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "ingests and interprets OpenTelemetry gen_ai spans",
      "to": "skill:llm-observability",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "one artifact across SaaS, self-host and BYOC",
      "to": "skill:multi-tenant-saas",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "backend services",
      "to": "skill:python-fastapi",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "note": "Helm and Terraform on Hetzner k3s",
      "to": "skill:terraform",
      "type": "skills"
    },
    {
      "from": "project:radicas",
      "to": "source:radicas-site",
      "type": "sources"
    },
    {
      "from": "project:radicas#claim-adr-count",
      "to": "source:github-profile",
      "type": "evidence"
    },
    {
      "from": "project:radicas#claim-backed-by-vento",
      "to": "experience:founder-in-residence-reef",
      "type": "evidence"
    },
    {
      "from": "project:radicas#claim-problem-to-first-users",
      "to": "experience:founder-in-residence-reef",
      "type": "evidence"
    },
    {
      "from": "project:radicas#claim-problem-to-first-users",
      "to": "experience:founder-in-residence-reef#highlight-zero-to-users",
      "type": "evidence"
    },
    {
      "from": "project:radicas#decision-eu-native-hosting",
      "to": "skill:terraform",
      "type": "skills"
    },
    {
      "from": "project:radicas#decision-single-artifact-deployment",
      "to": "skill:multi-tenant-saas",
      "type": "skills"
    },
    {
      "from": "project:radicas#decision-span-to-invoice-join",
      "to": "skill:clickhouse",
      "type": "skills"
    },
    {
      "from": "project:radicas#decision-span-to-invoice-join",
      "to": "skill:llm-observability",
      "type": "skills"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0019",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0037",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0052",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0053",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0054",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0056",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0057",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0058",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0059",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0060",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0061",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0070",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0085",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0086",
      "type": "sources"
    },
    {
      "from": "site:analytics-observability",
      "to": "source:adr-0087",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0001",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0002",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0003",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0004",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0005",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0006",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0007",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0008",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0009",
      "type": "sources"
    },
    {
      "from": "site:knowledge-layer",
      "to": "source:adr-0014",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0035",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0036",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0044",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0045",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0046",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0047",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0048",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0049",
      "type": "sources"
    },
    {
      "from": "site:memory-personalisation",
      "to": "source:adr-0056",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0039",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0040",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0041",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0043",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0050",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0062",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0073",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0081",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0082",
      "type": "sources"
    },
    {
      "from": "site:model-routing-cost-control",
      "to": "source:adr-0087",
      "type": "sources"
    },
    {
      "from": "site:real-metrics",
      "to": "source:adr-0039",
      "type": "sources"
    },
    {
      "from": "site:real-metrics",
      "to": "source:adr-0055",
      "type": "sources"
    },
    {
      "from": "site:real-metrics",
      "to": "source:adr-0057",
      "type": "sources"
    },
    {
      "from": "site:real-metrics",
      "to": "source:adr-0062",
      "type": "sources"
    },
    {
      "from": "site:real-metrics",
      "to": "source:adr-0081",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0030",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0038",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0039",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0040",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0042",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0043",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0044",
      "type": "sources"
    },
    {
      "from": "site:retrieval-context-engineering",
      "to": "source:adr-0062",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0011",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0012",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0013",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0014",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0015",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0016",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0017",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0019",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0020",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0069",
      "type": "sources"
    },
    {
      "from": "site:seo-geo-static-representation",
      "to": "source:adr-0085",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0020",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0030",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0031",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0032",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0033",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0034",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0041",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0042",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0055",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0063",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0065",
      "type": "sources"
    },
    {
      "from": "site:tool-calling-ui-control",
      "to": "source:adr-0074",
      "type": "sources"
    },
    {
      "from": "skill:llm-observability",
      "to": "source:otel-gen-ai",
      "type": "sources"
    }
  ],
  "schema_version": 1,
  "sections": {
    "experience:founder-in-residence-reef#highlight-selection": {
      "citable": true,
      "entity": "experience:founder-in-residence-reef",
      "kind": "highlight",
      "markdown": "Selected for the five-month full-time programme at OGR Torino, one of forty participants from several hundred applicants.",
      "order": 0,
      "text": "Selected for the five-month full-time programme at OGR Torino, one of forty participants from several hundred applicants.",
      "title": ""
    },
    "experience:founder-in-residence-reef#highlight-zero-to-users": {
      "citable": true,
      "entity": "experience:founder-in-residence-reef",
      "kind": "highlight",
      "markdown": "Took the product from zero to first users — problem discovery, architecture, implementation and go-to-market.",
      "order": 1,
      "text": "Took the product from zero to first users — problem discovery, architecture, implementation and go-to-market.",
      "title": ""
    },
    "experience:founder-radicas#highlight-cost-attribution": {
      "citable": true,
      "entity": "experience:founder-radicas",
      "kind": "highlight",
      "markdown": "Cost attribution and spend observability across multiple LLM providers, broken down per feature and per tenant, with budget alerting and anomaly detection.",
      "order": 0,
      "text": "Cost attribution and spend observability across multiple LLM providers, broken down per feature and per tenant, with budget alerting and anomaly detection.",
      "title": ""
    },
    "experience:founder-radicas#highlight-eval-gate": {
      "citable": true,
      "entity": "experience:founder-radicas",
      "kind": "highlight",
      "markdown": "Built the product's own AI layer with an eval harness gating every release and quality metrics tracked per commit.",
      "order": 2,
      "text": "Built the product's own AI layer with an eval harness gating every release and quality metrics tracked per commit.",
      "title": ""
    },
    "experience:founder-radicas#highlight-model-routing": {
      "citable": true,
      "entity": "experience:founder-radicas",
      "kind": "highlight",
      "markdown": "A routing layer that picks the model tier per request from task complexity, latency budget and cost ceiling.",
      "order": 1,
      "text": "A routing layer that picks the model tier per request from task complexity, latency budget and cost ceiling.",
      "title": ""
    },
    "experience:salento-racing-team#highlight-formula-sae": {
      "citable": true,
      "entity": "experience:salento-racing-team",
      "kind": "highlight",
      "markdown": "Built and maintained the electrical system of a Formula SAE car alongside the engineering degree.",
      "order": 0,
      "text": "Built and maintained the electrical system of a Formula SAE car alongside the engineering degree.",
      "title": ""
    },
    "experience:senior-swe-fincons-itv#highlight-integration-boundaries": {
      "citable": true,
      "entity": "experience:senior-swe-fincons-itv",
      "kind": "highlight",
      "markdown": "Architected and evolved Python services around SDVI Rally, defining integration boundaries and data contracts across ingest and orchestration flows.",
      "order": 0,
      "text": "Architected and evolved Python services around SDVI Rally, defining integration boundaries and data contracts across ingest and orchestration flows.",
      "title": ""
    },
    "experience:senior-swe-fincons-itv#highlight-supply-chain-automation": {
      "citable": true,
      "entity": "experience:senior-swe-fincons-itv",
      "kind": "highlight",
      "markdown": "Automated media supply-chain operations with AWS Lambda and DynamoDB on Terraform-backed CI/CD, with standardised observability and runbooks.",
      "order": 1,
      "text": "Automated media supply-chain operations with AWS Lambda and DynamoDB on Terraform-backed CI/CD, with standardised observability and runbooks.",
      "title": ""
    },
    "experience:swe-exprivia-enel#highlight-backend-algorithms": {
      "citable": true,
      "entity": "experience:swe-exprivia-enel",
      "kind": "highlight",
      "markdown": "Built algorithms and backend services on AWS serverless and Docker/Kubernetes, integrated with OpenText AppWorks.",
      "order": 1,
      "text": "Built algorithms and backend services on AWS serverless and Docker/Kubernetes, integrated with OpenText AppWorks.",
      "title": ""
    },
    "experience:swe-exprivia-enel#highlight-energy-systems": {
      "citable": true,
      "entity": "experience:swe-exprivia-enel",
      "kind": "highlight",
      "markdown": "Delivered Conceptual Design 2.0 for solar PV design, SDEE for dam data exchange, and EnelCheck 2.0 for plant safety auditing.",
      "order": 0,
      "text": "Delivered Conceptual Design 2.0 for solar PV design, SDEE for dam data exchange, and EnelCheck 2.0 for plant safety auditing.",
      "title": ""
    },
    "page:about#background": {
      "citable": true,
      "entity": "page:about",
      "kind": "free",
      "markdown": "A B.Sc. in Information Engineering at the University of Salento, with a year in the electrical division of its [Formula SAE team](../experience/salento-racing-team.md). Then backend services and algorithms for [Enel Green Power at Exprivia](../experience/swe-exprivia-enel.md) from 2018, and consultancy at Fincons Group, most recently [media supply-chain automation for ITV](../experience/senior-swe-fincons-itv.md). In 2026 he joined [Reef by Vento](../experience/founder-in-residence-reef.md), the venture-building programme where Radicas went from problem to first users.",
      "order": 2,
      "text": "A B.Sc. in Information Engineering at the University of Salento, with a year in the electrical division of its Formula SAE team. Then backend services and algorithms for Enel Green Power at Exprivia from 2018, and consultancy at Fincons Group, most recently media supply-chain automation for ITV. In 2026 he joined Reef by Vento, the venture-building programme where Radicas went from problem to first users.",
      "title": "Background"
    },
    "page:about#how-he-works": {
      "citable": true,
      "entity": "page:about",
      "kind": "free",
      "markdown": "Most of the work runs through coding agents that have been given the structure to work reliably: decisions written down before the code, knowledge the agents read before they act, and tests and review that decide what survives. The [principle](../principles/let-the-system-do-the-heavy-lifting.md) explains it with the projects where it shows.",
      "order": 1,
      "text": "Most of the work runs through coding agents that have been given the structure to work reliably: decisions written down before the code, knowledge the agents read before they act, and tests and review that decide what survives. The principle explains it with the projects where it shows.",
      "title": "How he works"
    },
    "page:about#what-he-works-on": {
      "citable": true,
      "entity": "page:about",
      "kind": "free",
      "markdown": "Agentic AI systems, and the parts that make them governable: cost attribution and model routing, eval harnesses that gate releases, tracing, and guardrails built into the runtime rather than added around it. [Radicas](../projects/radicas/index.md) measures what an AI feature costs against what it returns. [accreta](../projects/accreta/index.md) is a knowledge base an agent maintains, with every claim cited to its source. [Praxis](../projects/praxis/index.md) is a Go library for orchestrating LLM agents with the guardrails in the kernel.",
      "order": 0,
      "text": "Agentic AI systems, and the parts that make them governable: cost attribution and model routing, eval harnesses that gate releases, tracing, and guardrails built into the runtime rather than added around it. Radicas measures what an AI feature costs against what it returns. accreta is a knowledge base an agent maintains, with every claim cited to its source. Praxis is a Go library for orchestrating LLM agents with the guardrails in the kernel.",
      "title": "What he works on"
    },
    "page:privacy#assistant": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "Your question is sent in the body of the request, never in a web address a server receives. If you type it into the ask box on a content page, it is carried to `/ask` after the `#` of the address, which your browser keeps in its history and never sends. It then goes to two companies.\n\n**TypeSafe**, through Cloudflare's AI Gateway, receives your question alone, with the public list of my project and organisation names. It decides whether the question is about me, which language it is in, what it is about, and how likely it is to be an attempt to change the assistant's rules. **OpenAI** receives your question, the earlier turns of this conversation still in your tab, any text you selected on the page and chose to ask about, and the page you were on. It writes the answer.\n\n{table: processors; rows: TypeSafe, OpenAI}\n\n**This site keeps one record per question, and it contains no text.** It holds a random id for your tab's conversation, the page, which model answered and how many tokens it used, what it cost, how long it took, which of my pages it cited, and how the turn ended. It also holds **four things worked out from your question**: its language (English, Italian or other), what it is about in one of nine words (such as projects, skills or working with me), and two scores between 0 and 1, how likely the question is to be off-topic and how likely it is to be trying to change the assistant's rules. The topic word and the second score do nothing to you. The record also holds your IP address in scrambled form, with a key that changes every 24 hours, so records from different days cannot be linked. It is kept for 90 days, then only monthly totals remain. To stop abuse, the site also counts questions per address in memory, and that count disappears within a day.\n\n**Why:** to answer the question you asked, and to keep the assistant working, within its budget and safe. This is a legitimate interest (Art. 6(1)(f)). You choose to ask, the providers receive only what the answer needs, and this site keeps none of your words.\n\n**No automated decision about you:** the only thing decided automatically is whether the assistant answers. Every page stays open to you whatever it decides, and you can always write to me.",
      "order": 3,
      "text": "Your question is sent in the body of the request, never in a web address a server receives. If you type it into the ask box on a content page, it is carried to /ask after the # of the address, which your browser keeps in its history and never sends. It then goes to two companies.\n\nTypeSafe, through Cloudflare's AI Gateway, receives your question alone, with the public list of my project and organisation names. It decides whether the question is about me, which language it is in, what it is about, and how likely it is to be an attempt to change the assistant's rules. OpenAI receives your question, the earlier turns of this conversation still in your tab, any text you selected on the page and chose to ask about, and the page you were on. It writes the answer.\n\n{table: processors; rows: TypeSafe, OpenAI}\n\nThis site keeps one record per question, and it contains no text. It holds a random id for your tab's conversation, the page, which model answered and how many tokens it used, what it cost, how long it took, which of my pages it cited, and how the turn ended. It also holds four things worked out from your question: its language (English, Italian or other), what it is about in one of nine words (such as projects, skills or working with me), and two scores between 0 and 1, how likely the question is to be off-topic and how likely it is to be trying to change the assistant's rules. The topic word and the second score do nothing to you. The record also holds your IP address in scrambled form, with a key that changes every 24 hours, so records from different days cannot be linked. It is kept for 90 days, then only monthly totals remain. To stop abuse, the site also counts questions per address in memory, and that count disappears within a day.\n\nWhy: to answer the question you asked, and to keep the assistant working, within its budget and safe. This is a legitimate interest (Art. 6(1)(f)). You choose to ask, the providers receive only what the answer needs, and this site keeps none of your words.\n\nNo automated decision about you: the only thing decided automatically is whether the assistant answers. Every page stays open to you whatever it decides, and you can always write to me.",
      "title": "When you ask the assistant"
    },
    "page:privacy#changes": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "This page is generated from the same facts the site's design documents cite, and every change to it is a commit in the site's repository, which is private. The date at the top is when the providers' terms were last read.",
      "order": 8,
      "text": "This page is generated from the same facts the site's design documents cite, and every change to it is a commit in the site's repository, which is private. The date at the top is when the providers' terms were last read.",
      "title": "Changes"
    },
    "page:privacy#contact": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "The contact form asks for your address, your message, and optionally your name and what you need. You see everything on a review page before anything is sent, and none of your text is stored between the review and the send. The message goes by email, through Cloudflare's Email Routing, to my mailbox. My mailbox is kept by Google, in Gmail.\n\n{table: processors; rows: Cloudflare Email, Google (Gmail)}\n\nThis site keeps a record of the send without its content: which fields were filled, the categories you picked, and whether it was sent. The record is kept for 90 days, then only monthly totals remain. In my mailbox, a message stays as long as our conversation needs it. It is deleted by hand when you ask, because a mailbox has no automatic deletion that I could honestly promise.\n\n**Why:** to answer you. If you are writing about working together, the basis is taking steps at your request before a contract (Art. 6(1)(b)). For any other message, it is my legitimate interest in reading and replying to what you sent (Art. 6(1)(f)).",
      "order": 4,
      "text": "The contact form asks for your address, your message, and optionally your name and what you need. You see everything on a review page before anything is sent, and none of your text is stored between the review and the send. The message goes by email, through Cloudflare's Email Routing, to my mailbox. My mailbox is kept by Google, in Gmail.\n\n{table: processors; rows: Cloudflare Email, Google (Gmail)}\n\nThis site keeps a record of the send without its content: which fields were filled, the categories you picked, and whether it was sent. The record is kept for 90 days, then only monthly totals remain. In my mailbox, a message stays as long as our conversation needs it. It is deleted by hand when you ask, because a mailbox has no automatic deletion that I could honestly promise.\n\nWhy: to answer you. If you are writing about working together, the basis is taking steps at your request before a contract (Art. 6(1)(b)). For any other message, it is my legitimate interest in reading and replying to what you sent (Art. 6(1)(f)).",
      "title": "When you write to me"
    },
    "page:privacy#device": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "**No cookies.** Neither this site nor its host sets any. You can check this in your browser's developer tools, under Application → Cookies.\n\n**Nothing else is stored on your device**, except in one case:\n\n{table: storage}\n\nThat storage holds only what you typed into the assistant and what it answered. It never leaves your device except as part of your next question, and it goes when you close the tab. Because nothing is stored that you did not ask for, this site shows no cookie banner.",
      "order": 1,
      "text": "No cookies. Neither this site nor its host sets any. You can check this in your browser's developer tools, under Application → Cookies.\n\nNothing else is stored on your device, except in one case:\n\n{table: storage}\n\nThat storage holds only what you typed into the assistant and what it answered. It never leaves your device except as part of your next question, and it goes when you close the tab. Because nothing is stored that you did not ask for, this site shows no cookie banner.",
      "title": "On your device"
    },
    "page:privacy#reading": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "Every page is delivered by Cloudflare. Like any web host, it receives your IP address, the address of the page, and what your browser sends with every request. Content pages load one small script from this site, which only animates the page when you open or filter something; it sends nothing and stores nothing. There are no tracking pixels and nothing loaded from anyone else. `/ask` also loads the assistant's own script, from this site.\n\nCloudflare keeps its own analytics: a sample of requests, with IP address and path. I can see them for at least 31 days, and Cloudflare does not state a period for its own copy. Once a day, this site reads **how many times each page was requested** from those analytics and keeps that number. It keeps no IP address and nothing that could say who you are.\n\n**Why:** to deliver and protect the site, and to know which pages are read. This is a legitimate interest (Art. 6(1)(f)), and it involves nothing about you beyond what reaching a website always involves.",
      "order": 2,
      "text": "Every page is delivered by Cloudflare. Like any web host, it receives your IP address, the address of the page, and what your browser sends with every request. Content pages load one small script from this site, which only animates the page when you open or filter something; it sends nothing and stores nothing. There are no tracking pixels and nothing loaded from anyone else. /ask also loads the assistant's own script, from this site.\n\nCloudflare keeps its own analytics: a sample of requests, with IP address and path. I can see them for at least 31 days, and Cloudflare does not state a period for its own copy. Once a day, this site reads how many times each page was requested from those analytics and keeps that number. It keeps no IP address and nothing that could say who you are.\n\nWhy: to deliver and protect the site, and to know which pages are read. This is a legitimate interest (Art. 6(1)(f)), and it involves nothing about you beyond what reaching a website always involves.",
      "title": "When you read a page"
    },
    "page:privacy#retention": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "{table: surfaces}",
      "order": 6,
      "text": "{table: surfaces}",
      "title": "How long"
    },
    "page:privacy#rights": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "You can ask to see, correct or delete your data, to restrict or object to its processing, and to receive it in a portable form. Write to {contact}. You can object to anything this page says rests on a legitimate interest. On request I will explain how that interest was weighed against yours.\n\nTwo honest limits. **The per-question records cannot be linked to you**: they hold no name, no address and no key I could look you up by, so I cannot find yours to show or delete them. This is the design working, not a refusal. **A message in my mailbox** is found and deleted by hand.\n\nYou do not have to give anything: every page can be read without typing a word. If you think your data has been handled wrongly, you can complain to the [Garante per la protezione dei dati personali](https://www.garanteprivacy.it/diritti/come-agire-per-tutelare-i-tuoi-dati-personali/reclamo).",
      "order": 7,
      "text": "You can ask to see, correct or delete your data, to restrict or object to its processing, and to receive it in a portable form. Write to {contact}. You can object to anything this page says rests on a legitimate interest. On request I will explain how that interest was weighed against yours.\n\nTwo honest limits. The per-question records cannot be linked to you: they hold no name, no address and no key I could look you up by, so I cannot find yours to show or delete them. This is the design working, not a refusal. A message in my mailbox is found and deleted by hand.\n\nYou do not have to give anything: every page can be read without typing a word. If you think your data has been handled wrongly, you can complain to the Garante per la protezione dei dati personali.",
      "title": "Your rights"
    },
    "page:privacy#where": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "What this site stores itself is kept in the EU; Cloudflare keeps this site's request logs (Workers Logs) for 7 days in the United States. That is a claim about storage, not about the path your question takes. A request is handled at the Cloudflare location nearest you, and the two assistant providers process it in the United States, OpenAI on servers around the world.\n\n{table: transfers}\n\nThe Standard Contractual Clauses are Commission Decision (EU) 2021/914, [published on EUR-Lex](https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj).",
      "order": 5,
      "text": "What this site stores itself is kept in the EU; Cloudflare keeps this site's request logs (Workers Logs) for 7 days in the United States. That is a claim about storage, not about the path your question takes. A request is handled at the Cloudflare location nearest you, and the two assistant providers process it in the United States, OpenAI on servers around the world.\n\n{table: transfers}\n\nThe Standard Contractual Clauses are Commission Decision (EU) 2021/914, published on EUR-Lex.",
      "title": "Where your data goes"
    },
    "page:privacy#who": {
      "citable": true,
      "entity": "page:privacy",
      "kind": "free",
      "markdown": "Francesco Fiore, an individual in Italy, is responsible for the personal data this site processes. Write to {contact} about anything on this page. There is no data protection officer, because the law does not require one for a site like this.",
      "order": 0,
      "text": "Francesco Fiore, an individual in Italy, is responsible for the personal data this site processes. Write to {contact} about anything on this page. There is no data protection officer, because the law does not require one for a site like this.",
      "title": "Who is responsible"
    },
    "page:work-with-me#how-to-start": {
      "citable": true,
      "entity": "page:work-with-me",
      "kind": "free",
      "markdown": "The [contact form](/contact) asks for a message and where to reply. Everything else is optional: whether it is about a role, a project, advice or a collaboration, and, if it helps, what you are building and the problem in the way.",
      "order": 0,
      "text": "The contact form asks for a message and where to reply. Everything else is optional: whether it is about a role, a project, advice or a collaboration, and, if it helps, what you are building and the problem in the way.",
      "title": "How to start"
    },
    "principle:let-the-system-do-the-heavy-lifting#what-the-structure-actually-is": {
      "citable": true,
      "entity": "principle:let-the-system-do-the-heavy-lifting",
      "kind": "free",
      "markdown": "**Knowledge the agents read before they act, and update afterwards.** Living prose on architecture, contracts and invariants, with every non-trivial claim citing its source, and a check that says which pages a change has just made suspect. This is the pattern `accreta` extracts into a product.\n\n**Decisions written down before the code.** ADRs carrying the reasoning and what would change it, so a human and an agent argue from the same source of truth rather than from whatever fits in a chat window.\n\n**Tooling authored for the purpose.** Skills, subagents and hooks built for the task at hand, with one manifest generating the instruction file every agent expects and a `doctor` command that fails CI when they drift apart.\n\n**MCP as a delivery surface.** When something has a useful core it ships as an MCP server beside its CLI, so an assistant can drive it directly instead of being told about it.\n\n**Review and test discipline that does not bend.** The agent writes; the tests, the types and the review decide what survives. This is what separates the approach from generating code quickly and hoping.",
      "order": 0,
      "text": "Knowledge the agents read before they act, and update afterwards. Living prose on architecture, contracts and invariants, with every non-trivial claim citing its source, and a check that says which pages a change has just made suspect. This is the pattern accreta extracts into a product.\n\nDecisions written down before the code. ADRs carrying the reasoning and what would change it, so a human and an agent argue from the same source of truth rather than from whatever fits in a chat window.\n\nTooling authored for the purpose. Skills, subagents and hooks built for the task at hand, with one manifest generating the instruction file every agent expects and a doctor command that fails CI when they drift apart.\n\nMCP as a delivery surface. When something has a useful core it ships as an MCP server beside its CLI, so an assistant can drive it directly instead of being told about it.\n\nReview and test discipline that does not bend. The agent writes; the tests, the types and the review decide what survives. This is what separates the approach from generating code quickly and hoping.",
      "title": "What the structure actually is"
    },
    "principle:let-the-system-do-the-heavy-lifting#where-it-shows": {
      "citable": true,
      "entity": "principle:let-the-system-do-the-heavy-lifting",
      "kind": "free",
      "markdown": "The whole lifecycle runs this way — discovery, architecture, implementation, test and release. `accreta` went from first commit to a published package with all six planned phases complete in about a month. `claude-account-switcher` was built, tested and shipped with CI in a day. Radicas went from problem to first users inside a five-month programme, with around thirty ADRs behind it.\n\nThis repository is itself an instance: the brief decomposed into components, each open question closed by an ADR, and every decision written down with its reasons before the code that depends on it.",
      "order": 1,
      "text": "The whole lifecycle runs this way — discovery, architecture, implementation, test and release. accreta went from first commit to a published package with all six planned phases complete in about a month. claude-account-switcher was built, tested and shipped with CI in a day. Radicas went from problem to first users inside a five-month programme, with around thirty ADRs behind it.\n\nThis repository is itself an instance: the brief decomposed into components, each open question closed by an ADR, and every decision written down with its reasons before the code that depends on it.",
      "title": "Where it shows"
    },
    "project:accreta#claim-published-npm": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "claim",
      "markdown": "Published on npm and installable by anyone; the companion repository installs it from the registry rather than from source, so a broken package fails there.",
      "order": 9,
      "text": "Published on npm and installable by anyone; the companion repository installs it from the registry rather than from source, so a broken package fails there.",
      "title": ""
    },
    "project:accreta#claim-six-phases-in-a-month": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "claim",
      "markdown": "First commit to a published package with all six planned phases complete in about a month, across four releases.",
      "order": 10,
      "radar": "How was it built so quickly?",
      "text": "First commit to a published package with all six planned phases complete in about a month, across four releases.",
      "title": ""
    },
    "project:accreta#context": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "skeleton",
      "markdown": "Giving an agent knowledge of a large system usually means RAG: embed everything, retrieve chunks per question, hope the model assembles them. The context is rebuilt from scratch every time and nothing learned in one session survives into the next.",
      "order": 0,
      "text": "Giving an agent knowledge of a large system usually means RAG: embed everything, retrieve chunks per question, hope the model assembles them. The context is rebuilt from scratch every time and nothing learned in one session survives into the next.",
      "title": "Context"
    },
    "project:accreta#decision-compile-not-retrieve": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "decision",
      "markdown": "Following the LLM wiki pattern, the agent compiles knowledge once into interlinked Markdown pages and then keeps them current. The knowledge base becomes a compounding artefact rather than a lookup index, so cross-references and contradictions are already written down when a question arrives.",
      "order": 4,
      "radar": "Why compile a wiki instead of using RAG?",
      "text": "Following the LLM wiki pattern, the agent compiles knowledge once into interlinked Markdown pages and then keeps them current. The knowledge base becomes a compounding artefact rather than a lookup index, so cross-references and contradictions are already written down when a question arrives.",
      "title": "Compile knowledge into a wiki, do not retrieve it per query"
    },
    "project:accreta#decision-drift-detection": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "decision",
      "markdown": "Each page records the source revision it was last verified against, so when a source moves, `drift` names the pages that are now suspect. Documentation does not do this on its own, and it is the difference between a knowledge base and a pile of stale prose.",
      "order": 6,
      "radar": "How does it know a page has gone stale?",
      "text": "Each page records the source revision it was last verified against, so when a source moves, drift names the pages that are now suspect. Documentation does not do this on its own, and it is the difference between a knowledge base and a pile of stale prose.",
      "title": "Drift detection as a first-class command"
    },
    "project:accreta#decision-mcp-beside-cli": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "decision",
      "markdown": "The same core is reachable by a person at a terminal and by any agent speaking MCP, so search, page fetch, canonical lookup and impact analysis are available without a bespoke integration.",
      "order": 7,
      "radar": "Why ship an MCP server as well as a CLI?",
      "text": "The same core is reachable by a person at a terminal and by any agent speaking MCP, so search, page fetch, canonical lookup and impact analysis are available without a bespoke integration.",
      "title": "Ship an MCP server beside the CLI"
    },
    "project:accreta#decision-provenance-to-revision": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "decision",
      "markdown": "Every non-trivial claim cites the source it came from, including the line range and the revision. A page without citations is a page under suspicion. This is what makes the next decision possible.",
      "order": 5,
      "radar": "Why cite sources down to the revision?",
      "text": "Every non-trivial claim cites the source it came from, including the line range and the revision. A page without citations is a page under suspicion. This is what makes the next decision possible.",
      "title": "Provenance down to the revision"
    },
    "project:accreta#decisions": {
      "citable": false,
      "entity": "project:accreta",
      "kind": "skeleton",
      "markdown": "",
      "order": 3,
      "text": "",
      "title": "Decisions"
    },
    "project:accreta#problem": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "skeleton",
      "markdown": "A retrieval index is not an artefact that improves. Cross-references, synthesis and contradictions are re-derived on every query, at cost, and never written down. Worse, documentation of any kind goes stale silently: nothing tells you which pages a change to the underlying system has just invalidated.",
      "order": 1,
      "text": "A retrieval index is not an artefact that improves. Cross-references, synthesis and contradictions are re-derived on every query, at cost, and never written down. Worse, documentation of any kind goes stale silently: nothing tells you which pages a change to the underlying system has just invalidated.",
      "title": "Problem"
    },
    "project:accreta#results": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "skeleton",
      "markdown": "- Published on npm; all six planned phases complete and the pipeline runs end to end, with a worked example in the repository.\n- A companion repository exercises it against the IETF RFC series, installed from the registry, with drift running in CI against fixtures designed to make it go red.\n- The API is explicitly not yet stable.",
      "order": 8,
      "text": "Published on npm; all six planned phases complete and the pipeline runs end to end, with a worked example in the repository.\nA companion repository exercises it against the IETF RFC series, installed from the registry, with drift running in CI against fixtures designed to make it go red.\nThe API is explicitly not yet stable.",
      "title": "Results"
    },
    "project:accreta#role": {
      "citable": true,
      "entity": "project:accreta",
      "kind": "skeleton",
      "markdown": "Author and maintainer. Design, implementation and release.",
      "order": 2,
      "text": "Author and maintainer. Design, implementation and release.",
      "title": "Role"
    },
    "project:accreta-atlas#claim-drift-goes-red": {
      "citable": true,
      "entity": "project:accreta-atlas",
      "kind": "claim",
      "markdown": "CI installs accreta from npm and runs reindex, lint and drift as real assertions, with fixtures built to make drift go red.",
      "order": 1,
      "text": "CI installs accreta from npm and runs reindex, lint and drift as real assertions, with fixtures built to make drift go red.",
      "title": ""
    },
    "project:accreta-atlas#claim-rfc-corpus": {
      "citable": true,
      "entity": "project:accreta-atlas",
      "kind": "claim",
      "markdown": "The corpus is the IETF RFC series, vendored in the repository; a published RFC never changes, so its revision stays frozen and drift can run in CI.",
      "order": 0,
      "text": "The corpus is the IETF RFC series, vendored in the repository; a published RFC never changes, so its revision stays frozen and drift can run in CI.",
      "title": ""
    },
    "project:agentforge#claim-design-only": {
      "citable": true,
      "entity": "project:agentforge",
      "kind": "claim",
      "markdown": "The repository holds architecture decision records and subsystem specifications, with no implementation behind them.",
      "order": 1,
      "text": "The repository holds architecture decision records and subsystem specifications, with no implementation behind them.",
      "title": ""
    },
    "project:agentforge#claim-six-guardrail-layers": {
      "citable": true,
      "entity": "project:agentforge",
      "kind": "claim",
      "markdown": "The design places safety policy in six guardrail layers.",
      "order": 0,
      "text": "The design places safety policy in six guardrail layers.",
      "title": ""
    },
    "project:claude-account-switcher#claim-built-in-a-day": {
      "citable": true,
      "entity": "project:claude-account-switcher",
      "kind": "claim",
      "markdown": "Built, tested and shipped with CI in a single day.",
      "order": 0,
      "radar": "What made a one-day build possible?",
      "text": "Built, tested and shipped with CI in a single day.",
      "title": ""
    },
    "project:claude-account-switcher#claim-nothing-patched": {
      "citable": true,
      "entity": "project:claude-account-switcher",
      "kind": "claim",
      "markdown": "Nothing in Claude Code is patched; the tool uses Claude Code's own process-wrapper setting and its config-directory variable.",
      "order": 1,
      "text": "Nothing in Claude Code is patched; the tool uses Claude Code's own process-wrapper setting and its config-directory variable.",
      "title": ""
    },
    "project:coding-agent-sync#claim-doctor-fails-ci": {
      "citable": true,
      "entity": "project:coding-agent-sync",
      "kind": "claim",
      "markdown": "The doctor command validates the manifest and exits non-zero on drift, so CI catches it.",
      "order": 1,
      "text": "The doctor command validates the manifest and exits non-zero on drift, so CI catches it.",
      "title": ""
    },
    "project:coding-agent-sync#claim-one-manifest": {
      "citable": true,
      "entity": "project:coding-agent-sync",
      "kind": "claim",
      "markdown": "One agents.yaml manifest generates the instruction files for Codex, Claude Code, Gemini CLI, GitHub Copilot, Cursor, Windsurf, Continue and Cline.",
      "order": 0,
      "text": "One agents.yaml manifest generates the instruction files for Codex, Claude Code, Gemini CLI, GitHub Copilot, Cursor, Windsurf, Continue and Cline.",
      "title": ""
    },
    "project:disk-reclaim#claim-manual-reclaim": {
      "citable": true,
      "entity": "project:disk-reclaim",
      "kind": "claim",
      "markdown": "The manual investigation the tool came from reclaimed 118 GB in two hours, on a machine down to 1.4 GB free out of 460 GB.",
      "order": 0,
      "radar": "Where did all that space go?",
      "text": "The manual investigation the tool came from reclaimed 118 GB in two hours, on a machine down to 1.4 GB free out of 460 GB.",
      "title": ""
    },
    "project:disk-reclaim#claim-three-surfaces": {
      "citable": true,
      "entity": "project:disk-reclaim",
      "kind": "claim",
      "markdown": "Ships as a SwiftUI app, a CLI and an MCP server over one shared core.",
      "order": 1,
      "text": "Ships as a SwiftUI app, a CLI and an MCP server over one shared core.",
      "title": ""
    },
    "project:praxis#claim-apache-licence": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "claim",
      "markdown": "Released under Apache 2.0 and published on pkg.go.dev, with CI on the repository.",
      "order": 10,
      "text": "Released under Apache 2.0 and published on pkg.go.dev, with CI on the repository.",
      "title": ""
    },
    "project:praxis#claim-four-budget-dimensions": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "claim",
      "markdown": "The kernel enforces budgets in four dimensions — wall-clock time, LLM tokens, tool-call count and estimated cost — and a breach ends the invocation.",
      "order": 8,
      "text": "The kernel enforces budgets in four dimensions — wall-clock time, LLM tokens, tool-call count and estimated cost — and a breach ends the invocation.",
      "title": ""
    },
    "project:praxis#claim-mandatory-telemetry": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "claim",
      "markdown": "OpenTelemetry spans are a framework guarantee, emitted for every invocation without the application opting in.",
      "order": 9,
      "text": "OpenTelemetry spans are a framework guarantee, emitted for every invocation without the application opting in.",
      "title": ""
    },
    "project:praxis#context": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "skeleton",
      "markdown": "Most agent libraries are thin wrappers over a provider's HTTP API. That is the right shape for calling a model, and the wrong shape for a team that has to answer for what the agent did, what it cost and who authorised it.",
      "order": 0,
      "text": "Most agent libraries are thin wrappers over a provider's HTTP API. That is the right shape for calling a model, and the wrong shape for a team that has to answer for what the agent did, what it cost and who authorised it.",
      "title": "Context"
    },
    "project:praxis#decision-guardrails-in-kernel": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "decision",
      "markdown": "A typed invocation state machine with policy hooks and filter chains at every security-sensitive boundary, plus four-dimensional budget enforcement and a typed error taxonomy. The cost is overhead that a simple API call does not need — the README says so plainly and points at the thin SDKs for anyone who wants that instead.",
      "order": 4,
      "radar": "Why put the guardrails in the framework, not the app?",
      "text": "A typed invocation state machine with policy hooks and filter chains at every security-sensitive boundary, plus four-dimensional budget enforcement and a typed error taxonomy. The cost is overhead that a simple API call does not need — the README says so plainly and points at the thin SDKs for anyone who wants that instead.",
      "title": "Guardrails in the kernel, not in the application"
    },
    "project:praxis#decision-mandatory-telemetry": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "decision",
      "markdown": "OpenTelemetry is not an optional integration but a framework guarantee, so every invocation is traceable without the application opting in. Optional per-call identity signing sits alongside it.",
      "order": 6,
      "radar": "Why can't telemetry be turned off?",
      "text": "OpenTelemetry is not an optional integration but a framework guarantee, so every invocation is traceable without the application opting in. Optional per-call identity signing sits alongside it.",
      "title": "Telemetry is mandatory"
    },
    "project:praxis#decision-provider-agnostic": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "decision",
      "markdown": "Model access sits behind an interface, so the runtime is not bound to one vendor.",
      "order": 5,
      "radar": "Can I swap the model provider?",
      "text": "Model access sits behind an interface, so the runtime is not bound to one vendor.",
      "title": "Provider-agnostic LLM interface"
    },
    "project:praxis#decisions": {
      "citable": false,
      "entity": "project:praxis",
      "kind": "skeleton",
      "markdown": "",
      "order": 3,
      "text": "",
      "title": "Decisions"
    },
    "project:praxis#problem": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "skeleton",
      "markdown": "Governance added on top of an orchestration library is governance that can be bypassed. If policy checks, budgets and telemetry live in application code, every new call site is a chance to forget one, and there is no framework-level guarantee to point at during an audit.",
      "order": 1,
      "text": "Governance added on top of an orchestration library is governance that can be bypassed. If policy checks, budgets and telemetry live in application code, every new call site is a chance to forget one, and there is no framework-level guarantee to point at during an audit.",
      "title": "Problem"
    },
    "project:praxis#results": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "skeleton",
      "markdown": "- Apache 2.0, published on pkg.go.dev with CI on the repository.\n- The README states what the library is *not* for, which is the honest way to ship an opinionated runtime.",
      "order": 7,
      "text": "Apache 2.0, published on pkg.go.dev with CI on the repository.\nThe README states what the library is not for, which is the honest way to ship an opinionated runtime.",
      "title": "Results"
    },
    "project:praxis#role": {
      "citable": true,
      "entity": "project:praxis",
      "kind": "skeleton",
      "markdown": "Maintainer.",
      "order": 2,
      "text": "Maintainer.",
      "title": "Role"
    },
    "project:radicas#claim-adr-count": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "claim",
      "markdown": "Around thirty ADRs are written down behind the product, each with its reasoning and what would change it.",
      "order": 8,
      "text": "Around thirty ADRs are written down behind the product, each with its reasoning and what would change it.",
      "title": ""
    },
    "project:radicas#claim-backed-by-vento": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "claim",
      "markdown": "Built and backed inside Reef, the venture-building programme of Vento, Exor's early-stage VC arm.",
      "order": 10,
      "text": "Built and backed inside Reef, the venture-building programme of Vento, Exor's early-stage VC arm.",
      "title": ""
    },
    "project:radicas#claim-problem-to-first-users": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "claim",
      "markdown": "Went from problem to first users inside the five-month Reef by Vento programme.",
      "order": 9,
      "text": "Went from problem to first users inside the five-month Reef by Vento programme.",
      "title": ""
    },
    "project:radicas#context": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "skeleton",
      "markdown": "Teams shipping agentic AI features get a cloud bill and a token count, neither of which answers the question the business asks: what does this feature cost per use, and is it worth it. Provider consoles aggregate by account or by key, not by the feature or the tenant that caused the spend.",
      "order": 0,
      "text": "Teams shipping agentic AI features get a cloud bill and a token count, neither of which answers the question the business asks: what does this feature cost per use, and is it worth it. Provider consoles aggregate by account or by key, not by the feature or the tenant that caused the spend.",
      "title": "Context"
    },
    "project:radicas#decision-eu-native-hosting": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "decision",
      "markdown": "Helm and Terraform onto Hetzner k3s rather than a hyperscaler, with data residency in the EU.",
      "order": 5,
      "text": "Helm and Terraform onto Hetzner k3s rather than a hyperscaler, with data residency in the EU.",
      "title": "EU-native hosting on owned infrastructure"
    },
    "project:radicas#decision-single-artifact-deployment": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "decision",
      "markdown": "The same build ships as managed SaaS, as a self-hosted install and into a customer's own cloud, with one upgrade path across the three.",
      "order": 6,
      "text": "The same build ships as managed SaaS, as a self-hosted install and into a customer's own cloud, with one upgrade path across the three.",
      "title": "One artifact for SaaS, self-host and BYOC"
    },
    "project:radicas#decision-span-to-invoice-join": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "decision",
      "markdown": "Ingest OpenTelemetry `gen_ai` spans, price them in real time from a price book, then reconcile them span by span against FOCUS 1.3 invoice data when it arrives. The join is the core of the product, not a reporting feature on top of it.",
      "order": 4,
      "text": "Ingest OpenTelemetry gen_ai spans, price them in real time from a price book, then reconcile them span by span against FOCUS 1.3 invoice data when it arrives. The join is the core of the product, not a reporting feature on top of it.",
      "title": "Reconcile spans against invoice line items, and make that the product"
    },
    "project:radicas#decisions": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "skeleton",
      "markdown": "The reasoning behind these — the alternatives weighed and why they lost — is withheld while the product is live; see the withheld note in this page's metadata.",
      "order": 3,
      "text": "The reasoning behind these — the alternatives weighed and why they lost — is withheld while the product is live; see the withheld note in this page's metadata.",
      "title": "Decisions"
    },
    "project:radicas#problem": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "skeleton",
      "markdown": "Two sources of truth disagree by design. Instrumentation produces a cost *estimate* at the moment a call happens, computed from a price book. The provider's invoice is authoritative but lands a day or three later, and it is grouped by nothing the product cares about. Using only the estimate gives numbers nobody will sign off on; waiting for the invoice gives numbers that arrive too late to act on.",
      "order": 1,
      "text": "Two sources of truth disagree by design. Instrumentation produces a cost estimate at the moment a call happens, computed from a price book. The provider's invoice is authoritative but lands a day or three later, and it is grouped by nothing the product cares about. Using only the estimate gives numbers nobody will sign off on; waiting for the invoice gives numbers that arrive too late to act on.",
      "title": "Problem"
    },
    "project:radicas#results": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "skeleton",
      "markdown": "Assessed as of the date in the front matter; the product is in active development.\n\n- The span-to-line-item reconciliation runs end to end: estimated cost in real time, corrected against authoritative invoice data as it lands.\n- Around thirty ADRs record the reasoning behind the architecture.",
      "order": 7,
      "text": "Assessed as of the date in the front matter; the product is in active development.\n\nThe span-to-line-item reconciliation runs end to end: estimated cost in real time, corrected against authoritative invoice data as it lands.\nAround thirty ADRs record the reasoning behind the architecture.",
      "title": "Results"
    },
    "project:radicas#role": {
      "citable": true,
      "entity": "project:radicas",
      "kind": "skeleton",
      "markdown": "Founder and engineer. Problem discovery, architecture, implementation and go-to-market, inside the five-month Reef by Vento programme.",
      "order": 2,
      "text": "Founder and engineer. Problem discovery, architecture, implementation and go-to-market, inside the five-month Reef by Vento programme.",
      "title": "Role"
    },
    "site:analytics-observability#section-a-metric-sheet-instead-of-a-dashboard": {
      "citable": true,
      "entity": "site:analytics-observability",
      "kind": "free",
      "markdown": "Every metric in the brief is an expression over those fields with its denominator stated (ADR-0057). A command prints them as a sheet, and each rate carries its numerator and denominator, so a rate computed on four turns visibly is one. A zero denominator prints \"no data\", never 0% or 100%. From the first phase the sheet has the share of answers that cite something, the rate of unknown questions and of answers cut short, the rate of invented citations, tool success, latency against the timeouts, the most asked-about topics, how refusals happen, cost per conversation and per model, and cache behaviour.\n\nThree of the brief's metrics are declared unmeasurable rather than proxied:\n\n- **Time needed to find information.** A clock on a visitor is the measurement the bucket rule forbids. The sheet reports a different, differently named number instead: questions per conversation before the first answer that cites a page.\n- **Share of visitors who understand the positioning.** That needs asking people. Inferring it from scrolling would be surveillance.\n- **Opportunities attributable to the site.** Attribution ends at a message in my mailbox. What happens after is outside every system here.\n\nOne more has a numerator and no denominator. The share of interactions resolved without a model is the number the whole routing design aims at. But a followed link or a page read makes no request to the agent, so in the first phase there is nothing to divide by. It becomes computable only once visitors consent to analytics, which makes it the one headline metric that depends on someone saying yes.\n\nThere is no dashboard before the last phase, because a page with one reader is a surface to secure and host for a presentation improvement. What pushes is four alerts to one mailbox (ADR-0052): monthly spend passing 50% and 80%, the daily or provider cap being hit, rate limits refusing more than 5% of turns in a day, and the cache reading nothing for 20 turns in a row. An alert carries counters and names, never visitor text.",
      "order": 1,
      "text": "Every metric in the brief is an expression over those fields with its denominator stated (ADR-0057). A command prints them as a sheet, and each rate carries its numerator and denominator, so a rate computed on four turns visibly is one. A zero denominator prints \"no data\", never 0% or 100%. From the first phase the sheet has the share of answers that cite something, the rate of unknown questions and of answers cut short, the rate of invented citations, tool success, latency against the timeouts, the most asked-about topics, how refusals happen, cost per conversation and per model, and cache behaviour.\n\nThree of the brief's metrics are declared unmeasurable rather than proxied:\n\nTime needed to find information. A clock on a visitor is the measurement the bucket rule forbids. The sheet reports a different, differently named number instead: questions per conversation before the first answer that cites a page.\nShare of visitors who understand the positioning. That needs asking people. Inferring it from scrolling would be surveillance.\nOpportunities attributable to the site. Attribution ends at a message in my mailbox. What happens after is outside every system here.\n\nOne more has a numerator and no denominator. The share of interactions resolved without a model is the number the whole routing design aims at. But a followed link or a page read makes no request to the agent, so in the first phase there is nothing to divide by. It becomes computable only once visitors consent to analytics, which makes it the one headline metric that depends on someone saying yes.\n\nThere is no dashboard before the last phase, because a page with one reader is a surface to secure and host for a presentation improvement. What pushes is four alerts to one mailbox (ADR-0052): monthly spend passing 50% and 80%, the daily or provider cap being hit, rate limits refusing more than 5% of turns in a day, and the cache reading nothing for 20 turns in a row. An alert carries counters and names, never visitor text.",
      "title": "A metric sheet instead of a dashboard"
    },
    "site:analytics-observability#section-counting-pages-without-a-script": {
      "citable": true,
      "entity": "site:analytics-observability",
      "kind": "free",
      "markdown": "Content pages carry no tracking script in the first phase, only a 2 KB script that animates the layout and sends nothing, so the site cannot count readers the usual way. Once a day it reads the previous day's requests per page from Cloudflare's own zone analytics and keeps one total per route and day, with no address attached (ADR-0086). The number is Cloudflare's sampled estimate of HTML requests. It includes crawlers, since the free plan has no bot score. So it is labelled \"HTML requests (Cloudflare estimate)\" and never \"visitors\" or \"page views\". It is also not the missing denominator above: a request is not an interaction.\n\nNothing on a content page reports what you do there. The browser-side event vocabulary has a consent tier on every event, and in the first phase no event leaves the browser at all (ADR-0037, ADR-0053).",
      "order": 2,
      "text": "Content pages carry no tracking script in the first phase, only a 2 KB script that animates the layout and sends nothing, so the site cannot count readers the usual way. Once a day it reads the previous day's requests per page from Cloudflare's own zone analytics and keeps one total per route and day, with no address attached (ADR-0086). The number is Cloudflare's sampled estimate of HTML requests. It includes crawlers, since the free plan has no bot score. So it is labelled \"HTML requests (Cloudflare estimate)\" and never \"visitors\" or \"page views\". It is also not the missing denominator above: a request is not an interaction.\n\nNothing on a content page reports what you do there. The browser-side event vocabulary has a consent tier on every event, and in the first phase no event leaves the browser at all (ADR-0037, ADR-0053).",
      "title": "Counting pages without a script"
    },
    "site:analytics-observability#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:analytics-observability",
      "kind": "free",
      "markdown": "- **Measured**: no store this system owns has a field that could hold visitor text. The database refused four kinds of bad write on the infrastructure probe.\n- **Tested**: in the first phase, content pages carry no script beyond the 2 KB motion module, by the byte budget that fails the build and by a check against production after each deploy.\n- **Designed**: page counts are Cloudflare's sampled estimate of HTML requests, crawlers included.\n- **Designed**: three of the brief's metrics are not measured, and the share of interactions resolved without a model has no denominator in the first phase.\n- **Designed**: the deploy gate on the test set, and the record, the sheet and the alerts. None has seen a real visitor yet.\n- **Measured before launch**: the test set has been run against six models and graded by judges from two model families.",
      "order": 4,
      "text": "Measured: no store this system owns has a field that could hold visitor text. The database refused four kinds of bad write on the infrastructure probe.\nTested: in the first phase, content pages carry no script beyond the 2 KB motion module, by the byte budget that fails the build and by a check against production after each deploy.\nDesigned: page counts are Cloudflare's sampled estimate of HTML requests, crawlers included.\nDesigned: three of the brief's metrics are not measured, and the share of interactions resolved without a model has no denominator in the first phase.\nDesigned: the deploy gate on the test set, and the record, the sheet and the alerts. None has seen a real visitor yet.\nMeasured before launch: the test set has been run against six models and graded by judges from two model families.",
      "title": "How far this has been proved"
    },
    "site:analytics-observability#section-judging-the-answers": {
      "citable": true,
      "entity": "site:analytics-observability",
      "kind": "free",
      "markdown": "The quality of answers is checked against a test set written for the purpose, not collected from visitors, because collecting it would mean storing what visitors typed (ADR-0058). It has 51 test questions, each with the sections its answer should cite or the outcome it should have, 14 prompt-injection attempts, two held-out sets, and 8 deliberately bad answers that the grader must catch. Every expected section is a locked id, so a content change that moves one fails loudly.\n\nGrading has two layers (ADR-0059). Everything that set membership or a frame value can decide is asserted mechanically: citations resolve, destinations are real, no link or forbidden markup, the right tool was called. Only four things no assertion can reach go to a judge model: tone, depth, factual accuracy and honesty. The judge is a gate that fires below 3 out of 5, not a score anyone tracks. On 65 real answers it gave nothing below 3 and flagged nothing, so it was trusted only after it caught 8 bad answers out of 8. Two judges from different model families now grade, and each was measured slightly favouring its own family.\n\nThe set runs when one of four things changes: the instructions or tool definitions, the corpus, the model, or the generation settings (ADR-0060). A failed assertion blocks the deploy. A judge below 3 is reported to me, because a judge is an opinion and a rubric should not be a veto. When none of the four changed, results come from a cache and the run costs nothing.\n\nFrom the next phase an answer can be rated with one of three fixed values. There is no text box, because a feedback field that accepts a sentence is a store of visitor text with a helpful face (ADR-0061).",
      "order": 3,
      "text": "The quality of answers is checked against a test set written for the purpose, not collected from visitors, because collecting it would mean storing what visitors typed (ADR-0058). It has 51 test questions, each with the sections its answer should cite or the outcome it should have, 14 prompt-injection attempts, two held-out sets, and 8 deliberately bad answers that the grader must catch. Every expected section is a locked id, so a content change that moves one fails loudly.\n\nGrading has two layers (ADR-0059). Everything that set membership or a frame value can decide is asserted mechanically: citations resolve, destinations are real, no link or forbidden markup, the right tool was called. Only four things no assertion can reach go to a judge model: tone, depth, factual accuracy and honesty. The judge is a gate that fires below 3 out of 5, not a score anyone tracks. On 65 real answers it gave nothing below 3 and flagged nothing, so it was trusted only after it caught 8 bad answers out of 8. Two judges from different model families now grade, and each was measured slightly favouring its own family.\n\nThe set runs when one of four things changes: the instructions or tool definitions, the corpus, the model, or the generation settings (ADR-0060). A failed assertion blocks the deploy. A judge below 3 is reported to me, because a judge is an opinion and a rubric should not be a veto. When none of the four changed, results come from a cache and the run costs nothing.\n\nFrom the next phase an answer can be rated with one of three fixed values. There is no text box, because a feedback field that accepts a sentence is a store of visitor text with a helpful face (ADR-0061).",
      "title": "Judging the answers"
    },
    "site:analytics-observability#section-one-record-per-question": {
      "citable": true,
      "entity": "site:analytics-observability",
      "kind": "free",
      "markdown": "Each question produces one row, written once when the turn ends and never changed afterwards (ADR-0056). Every field is an id from the site's own list, a value from a closed set, or a number: which tier the turn reached, what the scope gate decided, what the question was about in one of nine words (ADR-0087), which rung of the fallback ladder served it, how it ended, which tools ran and how long each took, tokens in and out and how many were cached, the cost as the provider reported it, the latency, the sections cited, the citations the filter dropped, and the subject the assistant looked for when it had no answer. A write carrying anything outside its vocabulary is rejected, and the rejection counts as a defect.\n\nOne rule decides every duration. A duration that measures the service is a number. A duration that measures the person is a bucket or is not collected. Time to first token is a number. The time between your questions is one of five values, from \"first\" to \"over an hour\", because the cache decision needs only to know how many gaps fall between 5 and 60 minutes, and a finer clock would be a record of how long you thought.\n\nNot in the record: the message, the conversation, the selected text, the answer, the refusal, a user-agent string, a referrer, any model reasoning, and any key that could join the row to memory.",
      "order": 0,
      "text": "Each question produces one row, written once when the turn ends and never changed afterwards (ADR-0056). Every field is an id from the site's own list, a value from a closed set, or a number: which tier the turn reached, what the scope gate decided, what the question was about in one of nine words (ADR-0087), which rung of the fallback ladder served it, how it ended, which tools ran and how long each took, tokens in and out and how many were cached, the cost as the provider reported it, the latency, the sections cited, the citations the filter dropped, and the subject the assistant looked for when it had no answer. A write carrying anything outside its vocabulary is rejected, and the rejection counts as a defect.\n\nOne rule decides every duration. A duration that measures the service is a number. A duration that measures the person is a bucket or is not collected. Time to first token is a number. The time between your questions is one of five values, from \"first\" to \"over an hour\", because the cache decision needs only to know how many gaps fall between 5 and 60 minutes, and a finer clock would be a record of how long you thought.\n\nNot in the record: the message, the conversation, the selected text, the answer, the refusal, a user-agent string, a referrer, any model reasoning, and any key that could join the row to memory.",
      "title": "One record per question"
    },
    "site:guardrails-privacy-security#section-prompt-injection": {
      "citable": true,
      "entity": "site:guardrails-privacy-security",
      "kind": "free",
      "markdown": "Anything you send, and anything you select on a page, reaches the model in a labelled block that its instructions say to quote and never obey. That is a fence, and a fence can be leaned on. What actually stops an effect is the filter after the model: citations must be real ids, destinations must be real routes, and an answer cannot carry a link. A set of 14 injection attempts, through the message, through selected text, through a tool result and through a crafted conversation, ran clean on every mechanical condition for the model that answers here. Three of its conditions are judgements, such as whether an answer drifted off-topic. Two models from different companies graded those, and one of them is from the answering model's own family. That was one run, not a guarantee.",
      "order": 3,
      "text": "Anything you send, and anything you select on a page, reaches the model in a labelled block that its instructions say to quote and never obey. That is a fence, and a fence can be leaned on. What actually stops an effect is the filter after the model: citations must be real ids, destinations must be real routes, and an answer cannot carry a link. A set of 14 injection attempts, through the message, through selected text, through a tool result and through a crafted conversation, ran clean on every mechanical condition for the model that answers here. Three of its conditions are judgements, such as whether an answer drifted off-topic. Two models from different companies graded those, and one of them is from the answering model's own family. That was one run, not a guarantee.",
      "title": "Prompt injection"
    },
    "site:guardrails-privacy-security#section-what-i-decided-not-to-build": {
      "citable": true,
      "entity": "site:guardrails-privacy-security",
      "kind": "free",
      "markdown": "There is no moderation service in front of the assistant, because nothing a visitor writes is ever shown to anyone else. If that ever changes, moderation comes first: the threat model (ADR-0055) records that change as the trigger.",
      "order": 4,
      "text": "There is no moderation service in front of the assistant, because nothing a visitor writes is ever shown to anyone else. If that ever changes, moderation comes first: the threat model (ADR-0055) records that change as the trigger.",
      "title": "What I decided not to build"
    },
    "site:guardrails-privacy-security#section-what-leaves-it": {
      "citable": true,
      "entity": "site:guardrails-privacy-security",
      "kind": "free",
      "markdown": "A question travels in the body of a request, never in a query string, so no server log or analytics sample can hold it. One typed into the ask box on a content page reaches `/ask` after the `#` of the address, which stays in your own browser history and is never sent to a server. It goes to two companies. TypeSafe decides whether the question is about me. OpenAI writes the answer, and receives the question, the earlier turns and the page you are on. [Privacy](/privacy#assistant) lists what each receives and keeps, as read from their terms on the date shown there.\n\n{table: processors; rows: TypeSafe, OpenAI}\n\nWhat this site stores itself is in the EU; Cloudflare keeps its 7-day request logs (Workers Logs) in the United States. Both are claims about storage, not about the path your question takes.",
      "order": 1,
      "text": "A question travels in the body of a request, never in a query string, so no server log or analytics sample can hold it. One typed into the ask box on a content page reaches /ask after the # of the address, which stays in your own browser history and is never sent to a server. It goes to two companies. TypeSafe decides whether the question is about me. OpenAI writes the answer, and receives the question, the earlier turns and the page you are on. Privacy lists what each receives and keeps, as read from their terms on the date shown there.\n\n{table: processors; rows: TypeSafe, OpenAI}\n\nWhat this site stores itself is in the EU; Cloudflare keeps its 7-day request logs (Workers Logs) in the United States. Both are claims about storage, not about the path your question takes.",
      "title": "What leaves it"
    },
    "site:guardrails-privacy-security#section-what-stays-on-your-device": {
      "citable": true,
      "entity": "site:guardrails-privacy-security",
      "kind": "free",
      "markdown": "No cookies, from this site or from its host. On `/ask`, your conversation is kept in the tab's session storage and is gone when you close it. You can check both in your browser's developer tools. There is no consent banner because there is nothing to consent to. That is a result of building less, not of disclosing more.",
      "order": 0,
      "text": "No cookies, from this site or from its host. On /ask, your conversation is kept in the tab's session storage and is gone when you close it. You can check both in your browser's developer tools. There is no consent banner because there is nothing to consent to. That is a result of building less, not of disclosing more.",
      "title": "What stays on your device"
    },
    "site:guardrails-privacy-security#section-what-the-site-remembers": {
      "citable": true,
      "entity": "site:guardrails-privacy-security",
      "kind": "free",
      "markdown": "One record per question, with no text in it. It holds ids, counts, costs, timings, which pages were cited, and four things worked out from the question: its language, what it is about in one of nine words, and two scores for how likely it is to be off-topic or to be an attempt to change the rules. The topic and the second score are recorded and never acted on (ADR-0087). It flags explicit attempts and misses indirect ones, so it is evidence for a later decision, not a defence. Your address is kept only in a scrambled form whose key changes daily, so two days of records cannot be joined into one person.",
      "order": 2,
      "text": "One record per question, with no text in it. It holds ids, counts, costs, timings, which pages were cited, and four things worked out from the question: its language, what it is about in one of nine words, and two scores for how likely it is to be off-topic or to be an attempt to change the rules. The topic and the second score are recorded and never acted on (ADR-0087). It flags explicit attempts and misses indirect ones, so it is evidence for a later decision, not a defence. Your address is kept only in a scrambled form whose key changes daily, so two days of records cannot be joined into one person.",
      "title": "What the site remembers"
    },
    "site:knowledge-layer#section-designed-in-the-open": {
      "citable": true,
      "entity": "site:knowledge-layer",
      "kind": "free",
      "markdown": "The design came before the code. The brief was split into fourteen logical components in five layers, and each open question was closed by an architecture decision record before anything was built (ADR-0001). The brief, the deep-dives and every ADR are kept with the content, in the same private repository.\n\nThese How it works pages are summaries of that design, written by hand for a reader rather than copied from it. Each one records the documents it was written from and the commit at which they were read. A drift check lists every page whose sources have changed since, and for the pages that carry a privacy, security, cost or quality claim it blocks the merge (ADR-0009). A reader gets two depths, the summary and the topic page; the design documents behind them stay private.",
      "order": 4,
      "text": "The design came before the code. The brief was split into fourteen logical components in five layers, and each open question was closed by an architecture decision record before anything was built (ADR-0001). The brief, the deep-dives and every ADR are kept with the content, in the same private repository.\n\nThese How it works pages are summaries of that design, written by hand for a reader rather than copied from it. Each one records the documents it was written from and the commit at which they were read. A drift check lists every page whose sources have changed since, and for the pages that carry a privacy, security, cost or quality claim it blocks the merge (ADR-0009). A reader gets two depths, the summary and the topic page; the design documents behind them stay private.",
      "title": "Designed before it was built"
    },
    "site:knowledge-layer#section-facts-in-fields-prose-in-sections": {
      "citable": true,
      "entity": "site:knowledge-layer",
      "kind": "free",
      "markdown": "Each entity is one file. Facts that something has to compare, check or map to structured data live in front matter. Reasoning lives in prose under a heading skeleton the compiler lints (ADR-0004).\n\nA project comes in two depths. A case study must have context, problem, role, decisions and results, and each decision is its own anchored section with the alternatives it beat. An entry carries only the common fields, because forcing that skeleton onto a small utility produces padding.\n\nRelations are written once, on the newer or more specific entity, and the compiler inverts them. A new project names its skills, and nothing on the skill changes. The artefact can still answer \"what proves this skill\", and a skill that nothing proves fails the build. There are no self-rated levels.\n\nA result is a structured claim with its evidence, and its verifiability has three values: independent (someone else wrote the source), checkable (anyone can inspect the thing itself, such as a published package), or self-reported. A claim that cites my own profile is self-reported however public the profile is. Pages say which one applies in a sentence next to the claim, never as a badge (ADR-0014).",
      "order": 1,
      "text": "Each entity is one file. Facts that something has to compare, check or map to structured data live in front matter. Reasoning lives in prose under a heading skeleton the compiler lints (ADR-0004).\n\nA project comes in two depths. A case study must have context, problem, role, decisions and results, and each decision is its own anchored section with the alternatives it beat. An entry carries only the common fields, because forcing that skeleton onto a small utility produces padding.\n\nRelations are written once, on the newer or more specific entity, and the compiler inverts them. A new project names its skills, and nothing on the skill changes. The artefact can still answer \"what proves this skill\", and a skill that nothing proves fails the build. There are no self-rated levels.\n\nA result is a structured claim with its evidence, and its verifiability has three values: independent (someone else wrote the source), checkable (anyone can inspect the thing itself, such as a published package), or self-reported. A claim that cites my own profile is self-reported however public the profile is. Pages say which one applies in a sentence next to the claim, never as a badge (ADR-0014).",
      "title": "Facts in fields, prose in sections"
    },
    "site:knowledge-layer#section-ids-that-do-not-move": {
      "citable": true,
      "entity": "site:knowledge-layer",
      "kind": "free",
      "markdown": "Every entity has a typed id, `<type>:<key>`, separate from its URL slug, and every addressable section has an anchor built on it, `<entity-id>#<fragment>` (ADR-0006). One string serves four uses: it is the citation an answer carries, the unit the assistant reads, the id of the element on the page, and the target of a suggested question. This section is `site:knowledge-layer#section-ids-that-do-not-move`.\n\nEvery id and anchor is recorded in `ids.lock`, a committed file. Renaming a slug or a heading without recording an alias fails the check. Once production has served an id or anchor, CI rejects deleting its line, so from launch on the file only grows; before launch, a deletion is reported and passes. A citation stored in an old conversation or a test set keeps resolving after the prose around it is rewritten.",
      "order": 2,
      "text": "Every entity has a typed id, <type>:<key>, separate from its URL slug, and every addressable section has an anchor built on it, <entity-id>#<fragment> (ADR-0006). One string serves four uses: it is the citation an answer carries, the unit the assistant reads, the id of the element on the page, and the target of a suggested question. This section is site:knowledge-layer#section-ids-that-do-not-move.\n\nEvery id and anchor is recorded in ids.lock, a committed file. Renaming a slug or a heading without recording an alias fails the check. Once production has served an id or anchor, CI rejects deleting its line, so from launch on the file only grows; before launch, a deletion is reported and passes. A citation stored in an old conversation or a test set keeps resolving after the prose around it is rewritten.",
      "title": "Ids that do not move"
    },
    "site:knowledge-layer#section-one-artefact-many-readers": {
      "citable": true,
      "entity": "site:knowledge-layer",
      "kind": "free",
      "markdown": "The source is CommonMark with GitHub's extensions and YAML front matter, or plain YAML for structured entities. No MDX and no CMS: files in git, reviewed like code. The compiler runs four stages, load, validate, rules and emit, and reads `content/` and nothing else (ADR-0002).\n\nIts output is deterministic: sorted keys, stable order, no wall-clock value anywhere, and a `build_id` that is a hash of the content. The same content always builds the same bytes, which is what lets the site and the assistant prove they are on the same version. Section bodies ship as the original Markdown slice plus plain text, never as HTML, because rendering is the site's job. The artefact holds text I wrote and nothing else: external sources are cited, never ingested.\n\nThe compiler is my own, in TypeScript on unified/remark, with Zod 4 as the schema that also emits the JSON Schema published beside the artefact (ADR-0003). Velite, Astro's content collections and Contentlayer were read first. The hard parts here are sections, anchors, inverted relations and determinism, and none of them does those.",
      "order": 0,
      "text": "The source is CommonMark with GitHub's extensions and YAML front matter, or plain YAML for structured entities. No MDX and no CMS: files in git, reviewed like code. The compiler runs four stages, load, validate, rules and emit, and reads content/ and nothing else (ADR-0002).\n\nIts output is deterministic: sorted keys, stable order, no wall-clock value anywhere, and a build_id that is a hash of the content. The same content always builds the same bytes, which is what lets the site and the assistant prove they are on the same version. Section bodies ship as the original Markdown slice plus plain text, never as HTML, because rendering is the site's job. The artefact holds text I wrote and nothing else: external sources are cited, never ingested.\n\nThe compiler is my own, in TypeScript on unified/remark, with Zod 4 as the schema that also emits the JSON Schema published beside the artefact (ADR-0003). Velite, Astro's content collections and Contentlayer were read first. The hard parts here are sections, anchors, inverted relations and determinism, and none of them does those.",
      "title": "One artefact, many readers"
    },
    "site:knowledge-layer#section-what-ages-and-what-is-held-back": {
      "citable": true,
      "entity": "site:knowledge-layer",
      "kind": "free",
      "markdown": "Most facts do not expire, and the few that do carry a date. Availability, offerings, the profile and anything ongoing must record `as_of`, the day the statement was last confirmed, and each type has a review window (ADR-0007). Past it, nothing breaks. The page says \"Last confirmed {month}; not reconfirmed since.\", and the assistant gives the date with the fact. The compiler reads no clock, so the artefact is the same on any day, and each reader works out staleness against its own date. A retired entity becomes a tombstone that redirects or answers `410`.\n\nDrafts and anything confidential live in a second private repository, and the compiler has no way to read it. Confidential terms are turned into a scan that runs before every commit and again in CI, because pushed history is permanent and the only control that works is the one that runs before the push (ADR-0005). The scan is a tripwire, not a guarantee: it cannot catch a paraphrase, so review before publishing stays my job. A public entity can also mark a topic as withheld, so \"that part is not public\" is a different answer from \"that is not recorded\".\n\nEverything is written in English, because a second language is a second copy to keep in step (ADR-0008). The assistant can still answer in Italian, from the English source.",
      "order": 3,
      "text": "Most facts do not expire, and the few that do carry a date. Availability, offerings, the profile and anything ongoing must record as_of, the day the statement was last confirmed, and each type has a review window (ADR-0007). Past it, nothing breaks. The page says \"Last confirmed {month}; not reconfirmed since.\", and the assistant gives the date with the fact. The compiler reads no clock, so the artefact is the same on any day, and each reader works out staleness against its own date. A retired entity becomes a tombstone that redirects or answers 410.\n\nDrafts and anything confidential live in a second private repository, and the compiler has no way to read it. Confidential terms are turned into a scan that runs before every commit and again in CI, because pushed history is permanent and the only control that works is the one that runs before the push (ADR-0005). The scan is a tripwire, not a guarantee: it cannot catch a paraphrase, so review before publishing stays my job. A public entity can also mark a topic as withheld, so \"that part is not public\" is a different answer from \"that is not recorded\".\n\nEverything is written in English, because a second language is a second copy to keep in step (ADR-0008). The assistant can still answer in Italian, from the English source.",
      "title": "What ages and what is held back"
    },
    "site:known-limits#section-things-i-chose-knowing-the-cost": {
      "citable": true,
      "entity": "site:known-limits",
      "kind": "free",
      "markdown": "- The assistant forgets you when you close the tab. (ADR-0036)\n- A question it cannot place is recorded as a topic it looked for, never as your sentence, so the most useful editorial signal I could have is the one I gave up. What is left is one of nine words for what the question was about. (ADR-0087, ADR-0054)\n- Asking the assistant sends your words to two companies in the United States. I would rather tell you exactly which, and what they keep, than promise something I could not check. (ADR-0073)\n\nEach names the decision record behind it. Those records are not published.",
      "order": 1,
      "text": "The assistant forgets you when you close the tab. (ADR-0036)\nA question it cannot place is recorded as a topic it looked for, never as your sentence, so the most useful editorial signal I could have is the one I gave up. What is left is one of nine words for what the question was about. (ADR-0087, ADR-0054)\nAsking the assistant sends your words to two companies in the United States. I would rather tell you exactly which, and what they keep, than promise something I could not check. (ADR-0073)\n\nEach names the decision record behind it. Those records are not published.",
      "title": "Things I chose, knowing the cost"
    },
    "site:known-limits#section-things-this-site-has-not-proved": {
      "citable": true,
      "entity": "site:known-limits",
      "kind": "free",
      "markdown": "- The threat model is my own review of my own design. Nobody else has attacked it. (ADR-0055)\n- The reasoning that no cookie banner is needed, and the privacy notice itself, were written from the regulations and the regulators' guidance. No lawyer has read either. (ADR-0053, ADR-0083)\n- The injection results are one run per model, and three of their conditions are judged by models rather than checked by code. (ADR-0055, ADR-0062)\n- The scope gate refuses some questions whose writer introduces themselves first, such as a developer asking which library he uses: 4 of 25 in a set written to test this, none in its holdout. (ADR-0081)\n- The page counts are Cloudflare's estimate and include crawlers. (ADR-0086)\n- Three of the metrics I set out to track, such as the time it takes you to find something, are not measured at all, because the only way to measure them would be to watch you. (ADR-0057)",
      "order": 0,
      "text": "The threat model is my own review of my own design. Nobody else has attacked it. (ADR-0055)\nThe reasoning that no cookie banner is needed, and the privacy notice itself, were written from the regulations and the regulators' guidance. No lawyer has read either. (ADR-0053, ADR-0083)\nThe injection results are one run per model, and three of their conditions are judged by models rather than checked by code. (ADR-0055, ADR-0062)\nThe scope gate refuses some questions whose writer introduces themselves first, such as a developer asking which library he uses: 4 of 25 in a set written to test this, none in its holdout. (ADR-0081)\nThe page counts are Cloudflare's estimate and include crawlers. (ADR-0086)\nThree of the metrics I set out to track, such as the time it takes you to find something, are not measured at all, because the only way to measure them would be to watch you. (ADR-0057)",
      "title": "Things this site has not proved"
    },
    "site:memory-personalisation#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:memory-personalisation",
      "kind": "free",
      "markdown": "- **Designed**: no memory of any visitor in the first phase. Nothing is stored beyond the tab.\n- **Designed, not built**: everything under \"Memory, when it arrives\".\n- **Measured**: the interest profile above, over the site's own content, and the size of a full memory record as the assistant would read it, 173 tokens against a budget of 200.",
      "order": 4,
      "text": "Designed: no memory of any visitor in the first phase. Nothing is stored beyond the tab.\nDesigned, not built: everything under \"Memory, when it arrives\".\nMeasured: the interest profile above, over the site's own content, and the size of a full memory record as the assistant would read it, 173 tokens against a budget of 200.",
      "title": "How far this has been proved"
    },
    "site:memory-personalisation#section-memory-when-it-arrives": {
      "citable": true,
      "entity": "site:memory-personalisation",
      "kind": "free",
      "markdown": "Cross-session memory is designed and not built. It comes with a later phase, and every part of it is opt-in.\n\n- **Asked once, at the right moment.** Not a banner on arrival. The assistant asks only inside a panel you opened, after two questions, once per visit (ADR-0048). Declining writes nothing.\n- **An id that exists only after yes.** A random id is created in your browser at the moment you agree and never before, and it travels in the request body, not a cookie (ADR-0045).\n- **Six fields, no text.** The pages you explored, as ids, at most 12; the sections you asked about, at most 3; a depth preference; how often the assistant may suggest things; whether you opened the contact form; the first and last day you were seen, as dates (ADR-0046). Every value is an id from the site or a value from a fixed list, so memory cannot carry an injected instruction because it has nowhere to put one.\n- **Interests are worked out, never stored.** A subject counts as an interest only when at least two pages you opened belong to it, and interests are listed alphabetically, never ranked. They are recomputed every time they are read, so there is nothing to go stale.\n- **One writer, no model.** Only your browser writes the record, once per visit, and the server checks it against the schema. No model reads or writes memory, and the assistant has no memory tool (ADR-0047).\n- **See it, reset it, delete it.** The memory view shows the record itself. Delete removes the record and the id at once and leaves no trace to restore. How long a record is kept will be on the [privacy page](/privacy) from the day memory exists.\n\nMemory speaks about subjects, never about behaviour. \"You were interested in how accreta handles provenance\" is allowed. \"You've visited this page three times\" is not. The difference between useful and creepy is grammatical, so it is a rule the copy can be checked against.",
      "order": 2,
      "text": "Cross-session memory is designed and not built. It comes with a later phase, and every part of it is opt-in.\n\nAsked once, at the right moment. Not a banner on arrival. The assistant asks only inside a panel you opened, after two questions, once per visit (ADR-0048). Declining writes nothing.\nAn id that exists only after yes. A random id is created in your browser at the moment you agree and never before, and it travels in the request body, not a cookie (ADR-0045).\nSix fields, no text. The pages you explored, as ids, at most 12; the sections you asked about, at most 3; a depth preference; how often the assistant may suggest things; whether you opened the contact form; the first and last day you were seen, as dates (ADR-0046). Every value is an id from the site or a value from a fixed list, so memory cannot carry an injected instruction because it has nowhere to put one.\nInterests are worked out, never stored. A subject counts as an interest only when at least two pages you opened belong to it, and interests are listed alphabetically, never ranked. They are recomputed every time they are read, so there is nothing to go stale.\nOne writer, no model. Only your browser writes the record, once per visit, and the server checks it against the schema. No model reads or writes memory, and the assistant has no memory tool (ADR-0047).\nSee it, reset it, delete it. The memory view shows the record itself. Delete removes the record and the id at once and leaves no trace to restore. How long a record is kept will be on the privacy page from the day memory exists.\n\nMemory speaks about subjects, never about behaviour. \"You were interested in how accreta handles provenance\" is allowed. \"You've visited this page three times\" is not. The difference between useful and creepy is grammatical, so it is a rule the copy can be checked against.",
      "title": "Memory, when it arrives"
    },
    "site:memory-personalisation#section-nothing-outlives-the-tab": {
      "citable": true,
      "entity": "site:memory-personalisation",
      "kind": "free",
      "markdown": "On [/ask](/ask), your browser keeps one entry in the tab's session storage. It holds the conversation, trimmed to the last 8 turns or 8 KB, and a random id that groups the turns of this conversation (ADR-0036). The id travels in the body of each request, not in a cookie, and it is not joined to anything. Close the tab and both are gone. Nothing recognises you on your next visit, so there is nothing to ask your consent for.\n\nThe server holds nothing between questions. Your browser sends the conversation it wants the assistant to see, and the agent forgets it when the answer ends (ADR-0035). If your browser blocks storage, the conversation simply does not survive moving between pages. Nothing breaks and nothing asks you to change the setting.",
      "order": 0,
      "text": "On /ask, your browser keeps one entry in the tab's session storage. It holds the conversation, trimmed to the last 8 turns or 8 KB, and a random id that groups the turns of this conversation (ADR-0036). The id travels in the body of each request, not in a cookie, and it is not joined to anything. Close the tab and both are gone. Nothing recognises you on your next visit, so there is nothing to ask your consent for.\n\nThe server holds nothing between questions. Your browser sends the conversation it wants the assistant to see, and the agent forgets it when the answer ends (ADR-0035). If your browser blocks storage, the conversation simply does not survive moving between pages. Nothing breaks and nothing asks you to change the setting.",
      "title": "Nothing outlives the tab"
    },
    "site:memory-personalisation#section-what-adapts-without-memory": {
      "citable": true,
      "entity": "site:memory-personalisation",
      "kind": "free",
      "markdown": "Some personalisation needs no memory at all (ADR-0044). The page and section you asked from are part of the question, so an ambiguous question is read in their light. How deep an answer goes is taken from the question itself and from the section it came from: a question asked from a design decision gets the reasoning. No profile of the reader is built for this, and none is guessed. Whether you are a recruiter, a CTO or a founder is never inferred into anything.",
      "order": 1,
      "text": "Some personalisation needs no memory at all (ADR-0044). The page and section you asked from are part of the question, so an ambiguous question is read in their light. How deep an answer goes is taken from the question itself and from the section it came from: a question asked from a design decision gets the reasoning. No profile of the reader is built for this, and none is guessed. Whether you are a recruiter, a CTO or a founder is never inferred into anything.",
      "title": "What adapts without memory"
    },
    "site:memory-personalisation#section-why-the-profile-is-so-thin": {
      "citable": true,
      "entity": "site:memory-personalisation",
      "kind": "free",
      "markdown": "A ranked interest profile was measured before it was rejected (deep-dive 6). Over every possible visit to the pages that carry skills, the top-ranked category came out as backend or agentic delivery for 72.5% to 79.2% of visits, depending on how many pages were opened. That describes the portfolio's shape, not the visitor. Correcting for how common each category is only handed the win to whatever was rarest. The unranked set with a two-page threshold is the only version that says something about you without inventing it, and for a short visit it correctly says nothing.\n\nMemory also changes little on the page. Static pages are the same for everyone when they load, so anything reordered afterwards would shift the layout under you. Suggestions may be reordered. A list on a page is reordered only when it can be done without visible movement, and on the markup designed so far no list qualifies (ADR-0049).\n\nMemory and analytics are kept apart. The record of each question has no memory id and no field that could be joined to one (ADR-0056), so a deleted memory leaves nothing behind in the numbers.",
      "order": 3,
      "text": "A ranked interest profile was measured before it was rejected (deep-dive 6). Over every possible visit to the pages that carry skills, the top-ranked category came out as backend or agentic delivery for 72.5% to 79.2% of visits, depending on how many pages were opened. That describes the portfolio's shape, not the visitor. Correcting for how common each category is only handed the win to whatever was rarest. The unranked set with a two-page threshold is the only version that says something about you without inventing it, and for a short visit it correctly says nothing.\n\nMemory also changes little on the page. Static pages are the same for everyone when they load, so anything reordered afterwards would shift the layout under you. Suggestions may be reordered. A list on a page is reordered only when it can be done without visible movement, and on the markup designed so far no list qualifies (ADR-0049).\n\nMemory and analytics are kept apart. The record of each question has no memory id and no field that could be joined to one (ADR-0056), so a deleted memory leaves nothing behind in the numbers.",
      "title": "Why the profile is so thin"
    },
    "site:model-routing-cost-control#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:model-routing-cost-control",
      "kind": "free",
      "markdown": "- **Measured**: the scope gate refused 0% of in-scope questions on a 133-case set and on a 30-case holdout written separately, and it lets a question through whenever it cannot decide.\n- **Designed**: the $20 monthly cap on provider-side limits. The limits are set by hand before launch.\n- **Measured once, before launch**: the model comparison and the per-conversation cost above, on questions written for the purpose. No real visitor has asked anything yet.\n- **Measured from a local machine, not the edge**: the gate's latency, 0.49 s at the 95th percentile, against its 800 ms budget.",
      "order": 3,
      "text": "Measured: the scope gate refused 0% of in-scope questions on a 133-case set and on a 30-case holdout written separately, and it lets a question through whenever it cannot decide.\nDesigned: the $20 monthly cap on provider-side limits. The limits are set by hand before launch.\nMeasured once, before launch: the model comparison and the per-conversation cost above, on questions written for the purpose. No real visitor has asked anything yet.\nMeasured from a local machine, not the edge: the gate's latency, 0.49 s at the 95th percentile, against its 800 ms budget.",
      "title": "How far this has been proved"
    },
    "site:model-routing-cost-control#section-three-tiers-and-one-classifier": {
      "citable": true,
      "entity": "site:model-routing-cost-control",
      "kind": "free",
      "markdown": "**Tier 0 runs no model at all** (ADR-0040). It rejects an empty or over-long message, enforces the rate and budget limits, and answers a short list of questions about the assistant itself, such as whether you are talking to a person, from answers written in advance in English and Italian. Each of those answers still cites the page it quotes. The list is matched by rule. Letting a classifier match it was measured and declined, because it replaced real answers about the projects with canned ones about the site (ADR-0082).\n\n**Tier 1 is the one classifier in the system: a scope gate** (ADR-0081). It is a single call to Jev, a small decision model from TypeSafe reached through Cloudflare. It receives your message and the public list of Francesco's project and organisation names, and nothing else: no corpus, no conversation, no page context. It returns in, out or unclear, plus the language of the message. The turn is refused only when the gate puts more than half its probability on out. The refusal you then see is one of two sentences written in advance, one English and one Italian, so it cannot be talked into saying anything else. If the gate fails, returns something unreadable or takes longer than 800 ms, the question goes through. Refusing a recruiter by mistake is a product failure, while letting an off-topic question through costs a fraction of a cent.\n\nThe names are what made the gate work. Without them, every model tried called his own project names general knowledge: the gate as first specified refused 38% of the in-scope questions in the test set. With the 16 names, generated from the corpus at build time so a new project is admitted the day it is published, Jev refused none (deep-dive 16).\n\n**Tier 2 is the answering model**, with the corpus, the tools and a bounded loop of at most four tool calls and five model calls (ADR-0041). Nothing before it classifies intent or depth. The answering model makes both decisions anyway, with the whole corpus in front of it, and a second classifier would only add a way to route a question wrongly.",
      "order": 0,
      "text": "Tier 0 runs no model at all (ADR-0040). It rejects an empty or over-long message, enforces the rate and budget limits, and answers a short list of questions about the assistant itself, such as whether you are talking to a person, from answers written in advance in English and Italian. Each of those answers still cites the page it quotes. The list is matched by rule. Letting a classifier match it was measured and declined, because it replaced real answers about the projects with canned ones about the site (ADR-0082).\n\nTier 1 is the one classifier in the system: a scope gate (ADR-0081). It is a single call to Jev, a small decision model from TypeSafe reached through Cloudflare. It receives your message and the public list of Francesco's project and organisation names, and nothing else: no corpus, no conversation, no page context. It returns in, out or unclear, plus the language of the message. The turn is refused only when the gate puts more than half its probability on out. The refusal you then see is one of two sentences written in advance, one English and one Italian, so it cannot be talked into saying anything else. If the gate fails, returns something unreadable or takes longer than 800 ms, the question goes through. Refusing a recruiter by mistake is a product failure, while letting an off-topic question through costs a fraction of a cent.\n\nThe names are what made the gate work. Without them, every model tried called his own project names general knowledge: the gate as first specified refused 38% of the in-scope questions in the test set. With the 16 names, generated from the corpus at build time so a new project is admitted the day it is published, Jev refused none (deep-dive 16).\n\nTier 2 is the answering model, with the corpus, the tools and a bounded loop of at most four tool calls and five model calls (ADR-0041). Nothing before it classifies intent or depth. The answering model makes both decisions anyway, with the whole corpus in front of it, and a second classifier would only add a way to route a question wrongly.",
      "title": "Three tiers and one classifier"
    },
    "site:model-routing-cost-control#section-twenty-dollars-a-month": {
      "citable": true,
      "entity": "site:model-routing-cost-control",
      "kind": "free",
      "markdown": "The agent's spend is capped at $20 a month, and the cap is enforced by the providers rather than by a promise (ADR-0050, ADR-0073). The answering model runs in a dedicated project with a hard spending limit. The gate is paid from a prepaid balance with no automatic top-up, and an empty balance means the gate is skipped, not that the site stops. Inside that, the agent keeps three counters: 10 questions per conversation, a daily spend limit and the monthly one. Each address is limited to 12 questions an hour and 40 a day. Every limit is checked before any model runs, so a refused question costs nothing.\n\nWhen a counter runs out, the assistant drops to answers that need no model: the prepared answers and links to the site's pages, and otherwise an honest \"not right now\". It never switches itself to a cheaper model. A cheaper model is a quality decision, and it belongs to a person with a test set, not to a counter. I can switch the whole agent off with one setting. Every page keeps working on every one of these rungs.\n\nAt list prices read on 2026-09-22, a ten-question conversation with GPT-5.6 Luna costs about $0.0056 in answering calls, and a gate call about $0.00007, since it also records the question's topic (ADR-0087). So the $20 ceiling now allows far more traffic than a portfolio will see. The limits above were sized when the answering model cost 44 times more, and working them out again for the new price is still to do. Hosting is separate, about $6 a month. The monthly test runs have their own $5 budget.\n\nWhat is cached is the part of the prompt that never changes within a build: the instructions, the tool definitions and the corpus. There is no cache of answers and none of the gate's decisions, because either would be keyed on what visitors typed (ADR-0039).",
      "order": 2,
      "text": "The agent's spend is capped at $20 a month, and the cap is enforced by the providers rather than by a promise (ADR-0050, ADR-0073). The answering model runs in a dedicated project with a hard spending limit. The gate is paid from a prepaid balance with no automatic top-up, and an empty balance means the gate is skipped, not that the site stops. Inside that, the agent keeps three counters: 10 questions per conversation, a daily spend limit and the monthly one. Each address is limited to 12 questions an hour and 40 a day. Every limit is checked before any model runs, so a refused question costs nothing.\n\nWhen a counter runs out, the assistant drops to answers that need no model: the prepared answers and links to the site's pages, and otherwise an honest \"not right now\". It never switches itself to a cheaper model. A cheaper model is a quality decision, and it belongs to a person with a test set, not to a counter. I can switch the whole agent off with one setting. Every page keeps working on every one of these rungs.\n\nAt list prices read on 2026-09-22, a ten-question conversation with GPT-5.6 Luna costs about $0.0056 in answering calls, and a gate call about $0.00007, since it also records the question's topic (ADR-0087). So the $20 ceiling now allows far more traffic than a portfolio will see. The limits above were sized when the answering model cost 44 times more, and working them out again for the new price is still to do. Hosting is separate, about $6 a month. The monthly test runs have their own $5 budget.\n\nWhat is cached is the part of the prompt that never changes within a build: the instructions, the tool definitions and the corpus. There is no cache of answers and none of the gate's decisions, because either would be keyed on what visitors typed (ADR-0039).",
      "title": "Twenty dollars a month"
    },
    "site:model-routing-cost-control#section-which-model-answers": {
      "citable": true,
      "entity": "site:model-routing-cost-control",
      "kind": "free",
      "markdown": "GPT-5.6 Luna writes the answers (ADR-0062). It was chosen by disqualification. The pass mark was written before any candidate ran: all 14 injection cases clean, at least 49 of 51 test questions passed, at most 5 invented citations per 1,000, no answer below 3 out of 5 from either of two judge models, and no markup outside the allowed subset. Six models from two vendors were run over two rounds.\n\nIn the final round GPT-5.6 Luna passed all 51 test questions, all 28 held-out questions and all 14 injection cases, and invented none of its 153 citations. Two of its answers got a 2 from the Claude judge and passed with the OpenAI judge. I read both and accepted the model. That is a human decision over one criterion, recorded as such, and the pass mark is unchanged for the next model change. It needs the answer format enforced as a strict JSON schema: without the schema it passed 3 of 51.\n\nThe model sits behind a narrow interface of six capabilities, and its name is configuration (ADR-0043). Changing it is a deploy that has to pass the whole test set again first, like a change to the prompt or the corpus.",
      "order": 1,
      "text": "GPT-5.6 Luna writes the answers (ADR-0062). It was chosen by disqualification. The pass mark was written before any candidate ran: all 14 injection cases clean, at least 49 of 51 test questions passed, at most 5 invented citations per 1,000, no answer below 3 out of 5 from either of two judge models, and no markup outside the allowed subset. Six models from two vendors were run over two rounds.\n\nIn the final round GPT-5.6 Luna passed all 51 test questions, all 28 held-out questions and all 14 injection cases, and invented none of its 153 citations. Two of its answers got a 2 from the Claude judge and passed with the OpenAI judge. I read both and accepted the model. That is a human decision over one criterion, recorded as such, and the pass mark is unchanged for the next model change. It needs the answer format enforced as a strict JSON schema: without the schema it passed 3 of 51.\n\nThe model sits behind a narrow interface of six capabilities, and its name is configuration (ADR-0043). Changing it is a deploy that has to pass the whole test set again first, like a change to the prompt or the corpus.",
      "title": "Which model answers"
    },
    "site:real-metrics#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:real-metrics",
      "kind": "free",
      "markdown": "- **Designed**: every number on How it works says when and how it was measured, and the metrics published after launch come from the sheet with their denominators.\n- **Measured**: the three results above, each once, before launch.",
      "order": 3,
      "text": "Designed: every number on How it works says when and how it was measured, and the metrics published after launch come from the sheet with their denominators.\nMeasured: the three results above, each once, before launch.",
      "title": "How far this has been proved"
    },
    "site:real-metrics#section-measured-before-launch": {
      "citable": true,
      "entity": "site:real-metrics",
      "kind": "free",
      "markdown": "These were measured on sets of questions written for the purpose, not on visitors. Each links to the page that explains it.\n\n| What | Result | When and how |\n|---|---|---|\n| In-scope questions refused by the scope gate | 0%, on a 133-case set and on a 30-case holdout written separately | 2026-09-24, Jev with the list of project and organisation names, refusing only on a majority (ADR-0081). See [Model routing and cost control](/how-it-works/model-routing-cost-control). |\n| Prompt-injection attempts | 14 of 14 clean on every mechanical condition, for the model that answers here | One run per model, in deep-dive 11, September 2026. The three conditions that need judgement were graded by two judges from different companies, one of them from the answering model's own family (ADR-0062). See [Guardrails, privacy and security](/how-it-works/guardrails-privacy-security). |\n| Invented citations caught after generation | 1.9 per 1,000: one of 519 source ids did not exist | Two full runs of the test set in deep-dive 8, on an earlier answering model. The output filter catches exactly this, by set membership (ADR-0039). See [Retrieval and context engineering](/how-it-works/retrieval-context-engineering). |\n\nOne run, a few hundred cases and questions I wrote myself are enough to find a broken design. They are not enough to promise how the system behaves with real visitors, and nothing on these pages claims that they are.",
      "order": 2,
      "text": "These were measured on sets of questions written for the purpose, not on visitors. Each links to the page that explains it.\n\nWhat Result When and how\nIn-scope questions refused by the scope gate 0%, on a 133-case set and on a 30-case holdout written separately 2026-09-24, Jev with the list of project and organisation names, refusing only on a majority (ADR-0081). See Model routing and cost control.\nPrompt-injection attempts 14 of 14 clean on every mechanical condition, for the model that answers here One run per model, in deep-dive 11, September 2026. The three conditions that need judgement were graded by two judges from different companies, one of them from the answering model's own family (ADR-0062). See Guardrails, privacy and security.\nInvented citations caught after generation 1.9 per 1,000: one of 519 source ids did not exist Two full runs of the test set in deep-dive 8, on an earlier answering model. The output filter catches exactly this, by set membership (ADR-0039). See Retrieval and context engineering.\n\nOne run, a few hundred cases and questions I wrote myself are enough to find a broken design. They are not enough to promise how the system behaves with real visitors, and nothing on these pages claims that they are.",
      "title": "Measured before launch"
    },
    "site:real-metrics#section-the-rules-for-a-published-number": {
      "citable": true,
      "entity": "site:real-metrics",
      "kind": "free",
      "markdown": "- **Every measured number says when and how it was measured.** A measurement without a date and a method is not published.\n- **Every claim says how mature it is.** Designed means decided and not yet built. Tested means a check that runs asserts it. Measured means it was observed, with a number, at least once. A claim moves up only with its evidence (deep-dive 15).\n- **Every rate comes with its denominator.** Published metrics come from the same sheet I read, where each rate prints its numerator and denominator, and a zero denominator prints \"no data\" rather than 0% or 100% (ADR-0057).\n- **Nothing describes one person.** No transcript, no example question taken from a real session, and no aggregate small enough to point at one visitor. Examples on these pages are written by me and are not taken from anyone's session (ADR-0055).\n- **What cannot be measured stays unmeasured.** Three of the metrics I set out to track have no honest instrument, and they are not replaced by a proxy. [Analytics and observability](/how-it-works/analytics-observability) says which, and why.",
      "order": 0,
      "text": "Every measured number says when and how it was measured. A measurement without a date and a method is not published.\nEvery claim says how mature it is. Designed means decided and not yet built. Tested means a check that runs asserts it. Measured means it was observed, with a number, at least once. A claim moves up only with its evidence (deep-dive 15).\nEvery rate comes with its denominator. Published metrics come from the same sheet I read, where each rate prints its numerator and denominator, and a zero denominator prints \"no data\" rather than 0% or 100% (ADR-0057).\nNothing describes one person. No transcript, no example question taken from a real session, and no aggregate small enough to point at one visitor. Examples on these pages are written by me and are not taken from anyone's session (ADR-0055).\nWhat cannot be measured stays unmeasured. Three of the metrics I set out to track have no honest instrument, and they are not replaced by a proxy. Analytics and observability says which, and why.",
      "title": "The rules for a published number"
    },
    "site:real-metrics#section-what-will-be-published": {
      "citable": true,
      "entity": "site:real-metrics",
      "kind": "free",
      "markdown": "The candidates are the rows of the metric sheet that exist from the first phase: the share of answers that cite a source, how often the assistant had no answer and which topics it was asked about, the rate of invented citations caught by the filter, tool success, latency against the timeouts, how questions were refused, and cost per conversation and per model. Page counts are published as what they are, Cloudflare's sampled estimate of HTML requests, crawlers included.\n\nSome numbers arrive later or not at all. The share of interactions resolved without a model needs a denominator that exists only once visitors can consent to analytics. Feedback on answers, and anything about how suggestions are used, arrive with the phases that build them. The full dashboard, and a case study with metrics and lessons learned, belong to the last phase.",
      "order": 1,
      "text": "The candidates are the rows of the metric sheet that exist from the first phase: the share of answers that cite a source, how often the assistant had no answer and which topics it was asked about, the rate of invented citations caught by the filter, tool success, latency against the timeouts, how questions were refused, and cost per conversation and per model. Page counts are published as what they are, Cloudflare's sampled estimate of HTML requests, crawlers included.\n\nSome numbers arrive later or not at all. The share of interactions resolved without a model needs a denominator that exists only once visitors can consent to analytics. Feedback on answers, and anything about how suggestions are used, arrive with the phases that build them. The full dashboard, and a case study with metrics and lessons learned, belong to the last phase.",
      "title": "What will be published"
    },
    "site:retrieval-context-engineering#section-citations-are-checked-after-the-model-writes-them": {
      "citable": true,
      "entity": "site:retrieval-context-engineering",
      "kind": "free",
      "markdown": "A citation is an anchor, sent to your browser in its own frame beside the text rather than inside it. Every id the model emits has to pass two checks before it is streamed. It must be a live entity or a citable section in the artefact the site was built from, and it must name a document that was in the model's prompt. An id that fails either check is dropped and counted (ADR-0039). With no retrieval step, a cited anchor that was not in the prompt can only be an invention, and set membership catches it without anyone having to judge prose.\n\nThe filter is load-bearing, not defensive. In deep-dive 8, two full runs of the test set emitted 519 source ids and one of them did not exist: a correct section put under the wrong type prefix, on the line before the correct id for the same claim. That is 1.9 per 1,000. It happened on the second run of a question the first run had cited cleanly, so a single clean run proves nothing about grounding.\n\nThe corpus is projected once, when the agent starts, from the same `kb.json` the pages were built from. Changing content means deploying a new build, and the site and the agent always ship the same build together, so an answer cannot cite a section the live pages do not have. Staleness travels with each passage as data. Nothing else is cached: there is no cache of answers, because it would be keyed on what visitors typed.",
      "order": 3,
      "text": "A citation is an anchor, sent to your browser in its own frame beside the text rather than inside it. Every id the model emits has to pass two checks before it is streamed. It must be a live entity or a citable section in the artefact the site was built from, and it must name a document that was in the model's prompt. An id that fails either check is dropped and counted (ADR-0039). With no retrieval step, a cited anchor that was not in the prompt can only be an invention, and set membership catches it without anyone having to judge prose.\n\nThe filter is load-bearing, not defensive. In deep-dive 8, two full runs of the test set emitted 519 source ids and one of them did not exist: a correct section put under the wrong type prefix, on the line before the correct id for the same claim. That is 1.9 per 1,000. It happened on the second run of a question the first run had cited cleanly, so a single clean run proves nothing about grounding.\n\nThe corpus is projected once, when the agent starts, from the same kb.json the pages were built from. Changing content means deploying a new build, and the site and the agent always ship the same build together, so an answer cannot cite a section the live pages do not have. Staleness travels with each passage as data. Nothing else is cached: there is no cache of answers, because it would be keyed on what visitors typed.",
      "title": "Citations are checked after the model writes them"
    },
    "site:retrieval-context-engineering#section-four-layers-and-three-levels-of-trust": {
      "citable": true,
      "entity": "site:retrieval-context-engineering",
      "kind": "free",
      "markdown": "The prompt is assembled in four layers, ordered by how far each can be trusted and how often it changes (ADR-0042):\n\n1. the system instruction: role, perimeter, grounding and citation rules, language, output format;\n2. the tool definitions, generated from the tool contracts;\n3. the corpus, which I wrote and which the model may quote and cite but not obey;\n4. this turn: the earlier turns you sent, the page you are on, any text you selected, your message and any tool results.\n\nThe first three are the same bytes on every turn of a build, so the provider can cache them. The fourth is everything a visitor can influence. Each item in it sits in a labelled block, and the instruction says that nothing inside such a block is an instruction, whoever appears to be speaking. How that holds up against attempts to break it is on [Guardrails, privacy and security](/how-it-works/guardrails-privacy-security).\n\nThe fourth layer has a budget, because it is the part that is never cached (ADR-0044). The conversation so far is trimmed to 1,000 tokens, oldest turns first, and never summarised: a summary would cost a model call on every turn and would be one more thing that can lose a fact. A message is at most 1,000 characters, the page context at most 1 KB, and each tool result at most 1,000 tokens. The page and section you are reading are one sentence in the turn, which the model uses to break a tie when a question is ambiguous. They are a preference, not a filter. How deep to go is read from the question itself and from the section it was asked from. There is no profile of you to read it from.",
      "order": 1,
      "text": "The prompt is assembled in four layers, ordered by how far each can be trusted and how often it changes (ADR-0042):\n\nthe system instruction: role, perimeter, grounding and citation rules, language, output format;\nthe tool definitions, generated from the tool contracts;\nthe corpus, which I wrote and which the model may quote and cite but not obey;\nthis turn: the earlier turns you sent, the page you are on, any text you selected, your message and any tool results.\n\nThe first three are the same bytes on every turn of a build, so the provider can cache them. The fourth is everything a visitor can influence. Each item in it sits in a labelled block, and the instruction says that nothing inside such a block is an instruction, whoever appears to be speaking. How that holds up against attempts to break it is on Guardrails, privacy and security.\n\nThe fourth layer has a budget, because it is the part that is never cached (ADR-0044). The conversation so far is trimmed to 1,000 tokens, oldest turns first, and never summarised: a summary would cost a model call on every turn and would be one more thing that can lose a fact. A message is at most 1,000 characters, the page context at most 1 KB, and each tool result at most 1,000 tokens. The page and section you are reading are one sentence in the turn, which the model uses to break a tie when a question is ambiguous. They are a preference, not a filter. How deep to go is read from the question itself and from the section it was asked from. There is no profile of you to read it from.",
      "title": "Four layers and three levels of trust"
    },
    "site:retrieval-context-engineering#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:retrieval-context-engineering",
      "kind": "free",
      "markdown": "- **Measured**, 2026-09-20, on questions written for the purpose: the BM25 recall and the missing threshold above.\n- **Measured**, deep-dive 8: 1.9 fabricated ids per 1,000, caught by the filter. That run used an earlier answering model, not the one that answers here now.\n- **Designed**: the four layers, the budgets and the grounding rules.",
      "order": 4,
      "text": "Measured, 2026-09-20, on questions written for the purpose: the BM25 recall and the missing threshold above.\nMeasured, deep-dive 8: 1.9 fabricated ids per 1,000, caught by the filter. That run used an earlier answering model, not the one that answers here now.\nDesigned: the four layers, the budgets and the grounding rules.",
      "title": "How far this has been proved"
    },
    "site:retrieval-context-engineering#section-no-index-at-all": {
      "citable": true,
      "entity": "site:retrieval-context-engineering",
      "kind": "free",
      "markdown": "Retrieval was built before it was rejected (ADR-0038). On 2026-09-20 a BM25 index over the projected corpus was run against 27 answerable questions written for the purpose. At the five passages a turn can afford, it found a supporting passage for 82% of the English questions and 60% of the Italian ones. So nearly one English question in five that the corpus could answer would have come back as \"I don't know\", and each would have been filed as a content gap that does not exist. The relevance threshold meant to separate answerable questions from unanswerable ones did not exist either: 9 of the 26 answerable questions that returned anything scored at or below the best-scoring unanswerable one.\n\nLoading everything was cheaper than the machinery that would select part of it. The corpus was measured at about 4,200 tokens that day. That figure was counted with an OpenAI tokenizer, and the corpus has grown since. With these how-it-works pages it reached about 25,000 tokens, past the ceiling below. So these pages now enter the prompt as their summary and opening only, and the assistant points to them for the rest, which keeps the corpus near 11,400 tokens (ADR-0038). So there is no vector store, no embedding model, no reranker, and not the BM25 index that was measured. Recall is complete by construction, because every passage of the portfolio is in context on every turn.\n\nThe unit of the corpus is the anchor: one document per addressable section, labelled with its id. There is no chunking to tune, because the boundaries are the ones I wrote. Before the documents comes a catalogue of every entity, with its `as_of` date, any topic marked withheld, and for each skill the work that proves it. Because everything the corpus holds is listed, \"that is not published here\" is a fact the model can see, not an inference from a failed search.\n\nThis is the argument of accreta's own [compile, don't retrieve](/projects/accreta#decision-compile-not-retrieve) decision, applied to this site. It has a shelf life, and the limit is written down: CI fails the build when the projected corpus passes 20,000 tokens, and the BM25 configuration measured here is recorded as the design that replaces it.",
      "order": 0,
      "text": "Retrieval was built before it was rejected (ADR-0038). On 2026-09-20 a BM25 index over the projected corpus was run against 27 answerable questions written for the purpose. At the five passages a turn can afford, it found a supporting passage for 82% of the English questions and 60% of the Italian ones. So nearly one English question in five that the corpus could answer would have come back as \"I don't know\", and each would have been filed as a content gap that does not exist. The relevance threshold meant to separate answerable questions from unanswerable ones did not exist either: 9 of the 26 answerable questions that returned anything scored at or below the best-scoring unanswerable one.\n\nLoading everything was cheaper than the machinery that would select part of it. The corpus was measured at about 4,200 tokens that day. That figure was counted with an OpenAI tokenizer, and the corpus has grown since. With these how-it-works pages it reached about 25,000 tokens, past the ceiling below. So these pages now enter the prompt as their summary and opening only, and the assistant points to them for the rest, which keeps the corpus near 11,400 tokens (ADR-0038). So there is no vector store, no embedding model, no reranker, and not the BM25 index that was measured. Recall is complete by construction, because every passage of the portfolio is in context on every turn.\n\nThe unit of the corpus is the anchor: one document per addressable section, labelled with its id. There is no chunking to tune, because the boundaries are the ones I wrote. Before the documents comes a catalogue of every entity, with its as_of date, any topic marked withheld, and for each skill the work that proves it. Because everything the corpus holds is listed, \"that is not published here\" is a fact the model can see, not an inference from a failed search.\n\nThis is the argument of accreta's own compile, don't retrieve decision, applied to this site. It has a shelf life, and the limit is written down: CI fails the build when the projected corpus passes 20,000 tokens, and the BM25 configuration measured here is recorded as the design that replaces it.",
      "title": "No index at all"
    },
    "site:retrieval-context-engineering#section-what-the-assistant-may-say": {
      "citable": true,
      "entity": "site:retrieval-context-engineering",
      "kind": "free",
      "markdown": "The grounding rules are written as rules rather than as a tone (ADR-0042, ADR-0030):\n\n- Every factual claim carries at least one source id. A sentence that cannot cite is not written.\n- A fact has three states. A value is stated. A withheld topic gets the site's fixed sentence, \"{Topic} is not public — {reason}.\", and nothing is said around it, not even as the assistant's own reading. An absent one is stated as not published here, and the topic it was looking for is recorded, never your sentence.\n- A fact with a stale date is given with its date, never restated as if it were current.\n- The model's own knowledge of the world is not a source.\n- Anything the corpus does not say outright is marked as the assistant's reading.\n- It answers in English or Italian, following your language. Ids, titles and quoted claims stay in their English form, because a translated claim is a new claim.\n\nThe assistant is software and says so if asked. It speaks about Francesco, not as him, and what it knows is what this site publishes.",
      "order": 2,
      "text": "The grounding rules are written as rules rather than as a tone (ADR-0042, ADR-0030):\n\nEvery factual claim carries at least one source id. A sentence that cannot cite is not written.\nA fact has three states. A value is stated. A withheld topic gets the site's fixed sentence, \"{Topic} is not public — {reason}.\", and nothing is said around it, not even as the assistant's own reading. An absent one is stated as not published here, and the topic it was looking for is recorded, never your sentence.\nA fact with a stale date is given with its date, never restated as if it were current.\nThe model's own knowledge of the world is not a source.\nAnything the corpus does not say outright is marked as the assistant's reading.\nIt answers in English or Italian, following your language. Ids, titles and quoted claims stay in their English form, because a translated claim is a new claim.\n\nThe assistant is software and says so if asked. It speaks about Francesco, not as him, and what it knows is what this site publishes.",
      "title": "What the assistant may say"
    },
    "site:seo-geo-static-representation#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:seo-geo-static-representation",
      "kind": "free",
      "markdown": "- **Tested**: in the first phase, content pages carry at most the 2 KB motion script and nothing injected. The byte budget fails the build, and the post-deploy check asserts it on production.\n- **Designed**: the performance budgets, the accessibility floor, the structured data and the crawler policy. They have not yet been measured on real traffic.",
      "order": 3,
      "text": "Tested: in the first phase, content pages carry at most the 2 KB motion script and nothing injected. The byte budget fails the build, and the post-deploy check asserts it on production.\nDesigned: the performance budgets, the accessibility floor, the structured data and the crawler policy. They have not yet been measured on real traffic.",
      "title": "How far this has been proved"
    },
    "site:seo-geo-static-representation#section-readable-by-machines": {
      "citable": true,
      "entity": "site:seo-geo-static-representation",
      "kind": "free",
      "markdown": "Each page carries one JSON-LD graph, and every node's `@id` is derived from the canonical URL of the entity it describes, so the same project referenced from two pages is the same node (ADR-0015). The profile is a `ProfilePage` over a `Person`. A case study is a `TechArticle` with one part per design decision, so the reasoning is addressable by a machine as well as by the assistant. Indexes are `CollectionPage`s. There is no `FAQPage`: its rich results stopped appearing in May 2026, and the value here is a consistent graph, not a result type. In that graph, `worksFor` names the company that employed me, never the client the work was delivered for.\n\nEvery documented AI crawler is allowed, training included, and each is named in `robots.txt` so the policy is on record rather than implied (ADR-0016). Nothing here is a secret, and a portfolio a model has read is one it can recommend. There is no `llms.txt`. In 2026 one study found about one domain in ten publishing one, another found 97% of the files it examined were never requested, and Google says such files are not needed. The day a crawler operator documents reading it, that changes.\n\nThe one machine-readable export is the artefact itself. `kb.json` and its JSON Schema are published at stable URLs and linked from How it works, and the sitemap is generated from the route table. Nothing on the site reads the published copy: pages are built from the artefact directly.\n\nThe CV is a view of the site. `/cv` is rendered from the same artefact, current roles first with overlapping roles shown as overlapping, and the PDF is printed from that page at build time (ADR-0017). A CV and a site cannot disagree when one is generated from the other.",
      "order": 2,
      "text": "Each page carries one JSON-LD graph, and every node's @id is derived from the canonical URL of the entity it describes, so the same project referenced from two pages is the same node (ADR-0015). The profile is a ProfilePage over a Person. A case study is a TechArticle with one part per design decision, so the reasoning is addressable by a machine as well as by the assistant. Indexes are CollectionPages. There is no FAQPage: its rich results stopped appearing in May 2026, and the value here is a consistent graph, not a result type. In that graph, worksFor names the company that employed me, never the client the work was delivered for.\n\nEvery documented AI crawler is allowed, training included, and each is named in robots.txt so the policy is on record rather than implied (ADR-0016). Nothing here is a secret, and a portfolio a model has read is one it can recommend. There is no llms.txt. In 2026 one study found about one domain in ten publishing one, another found 97% of the files it examined were never requested, and Google says such files are not needed. The day a crawler operator documents reading it, that changes.\n\nThe one machine-readable export is the artefact itself. kb.json and its JSON Schema are published at stable URLs and linked from How it works, and the sitemap is generated from the route table. Nothing on the site reads the published copy: pages are built from the artefact directly.\n\nThe CV is a view of the site. /cv is rendered from the same artefact, current roles first with overlapping roles shown as overlapping, and the PDF is printed from that page at build time (ADR-0017). A CV and a site cannot disagree when one is generated from the other.",
      "title": "Readable by machines"
    },
    "site:seo-geo-static-representation#section-routes-and-anchors-that-stay-put": {
      "citable": true,
      "entity": "site:seo-geo-static-representation",
      "kind": "free",
      "markdown": "There is one route per page-bearing entity, and a page shows the sections of at most one entity, so every section id is unique on the page that serves it (ADR-0011). Every id resolves to a URL. A renamed page answers with a permanent redirect. A retired one redirects to its successor, or answers `410` with a short page saying when and why it was retired. Canonical URLs have no trailing slash. Because section anchors are locked (see [Knowledge layer](/how-it-works/knowledge-layer)), a link to a decision keeps landing on that decision after the prose around it is rewritten.",
      "order": 1,
      "text": "There is one route per page-bearing entity, and a page shows the sections of at most one entity, so every section id is unique on the page that serves it (ADR-0011). Every id resolves to a URL. A renamed page answers with a permanent redirect. A retired one redirects to its successor, or answers 410 with a short page saying when and why it was retired. Canonical URLs have no trailing slash. Because section anchors are locked (see Knowledge layer), a link to a decision keeps landing on that decision after the prose around it is rewritten.",
      "title": "Routes and anchors that stay put"
    },
    "site:seo-geo-static-representation#section-static-first": {
      "citable": true,
      "entity": "site:seo-geo-static-representation",
      "kind": "free",
      "markdown": "Every route is rendered to HTML at build time, rebuilt when content changes and once a day, and published all at once under one build id (ADR-0012). The shortest review window on any fact is 30 days, so per-request rendering would buy nothing, and static output is the only kind that is still correct when every backend is down. A page always prints the date a volatile fact was confirmed. The daily build switches it to \"not reconfirmed since\" within a day of its review window passing.\n\nThe site is built with Astro from `kb.json` as plain build-time data (ADR-0013). Section Markdown goes through the same parser and plugins the compiler uses, so a heading or a table cannot mean one thing on the page and another to the assistant. Section ids on the page are the anchors from the artefact, never derived again from heading text.\n\nIn the first phase, content pages carry one first-party script of at most 2 KB compressed, which only animates islands moving when the visitor opens or filters something; every page reads and works the same without it, and shipping more fails the build (ADR-0019). When the assistant later moves onto content pages, its script is capped at 60 KB compressed and loads after the page is usable. Until then the only page that loads the assistant is [/ask](/ask), and its script is the site's own (ADR-0020). The host is held to the same rule. The Cloudflare features that inject scripts into pages are switched off in configuration, HTML is served with a header that forbids rewriting it, and a check after every deploy asserts that production serves no injected script (ADR-0085).\n\nThe other budgets are numbers that fail the build too: Largest Contentful Paint under 2.5 s, Interaction to Next Paint at most 200 ms, layout shift under 0.1, CSS at most 50 KB compressed and fonts at most 120 KB in total. Accessibility is held to WCAG 2.2 AA.\n\nOne Cloudflare Worker on one domain serves the pages, the assistant and the contact form, and every change ships as a single upload (ADR-0069). Pages are served as static files without running the Worker. Because the site and the agent ship together, an answer can never cite a section the live pages do not have. If the assistant is off or unreachable, every page is exactly as it would be without it.",
      "order": 0,
      "text": "Every route is rendered to HTML at build time, rebuilt when content changes and once a day, and published all at once under one build id (ADR-0012). The shortest review window on any fact is 30 days, so per-request rendering would buy nothing, and static output is the only kind that is still correct when every backend is down. A page always prints the date a volatile fact was confirmed. The daily build switches it to \"not reconfirmed since\" within a day of its review window passing.\n\nThe site is built with Astro from kb.json as plain build-time data (ADR-0013). Section Markdown goes through the same parser and plugins the compiler uses, so a heading or a table cannot mean one thing on the page and another to the assistant. Section ids on the page are the anchors from the artefact, never derived again from heading text.\n\nIn the first phase, content pages carry one first-party script of at most 2 KB compressed, which only animates islands moving when the visitor opens or filters something; every page reads and works the same without it, and shipping more fails the build (ADR-0019). When the assistant later moves onto content pages, its script is capped at 60 KB compressed and loads after the page is usable. Until then the only page that loads the assistant is /ask, and its script is the site's own (ADR-0020). The host is held to the same rule. The Cloudflare features that inject scripts into pages are switched off in configuration, HTML is served with a header that forbids rewriting it, and a check after every deploy asserts that production serves no injected script (ADR-0085).\n\nThe other budgets are numbers that fail the build too: Largest Contentful Paint under 2.5 s, Interaction to Next Paint at most 200 ms, layout shift under 0.1, CSS at most 50 KB compressed and fonts at most 120 KB in total. Accessibility is held to WCAG 2.2 AA.\n\nOne Cloudflare Worker on one domain serves the pages, the assistant and the contact form, and every change ships as a single upload (ADR-0069). Pages are served as static files without running the Worker. Because the site and the agent ship together, an answer can never cite a section the live pages do not have. If the assistant is off or unreachable, every page is exactly as it would be without it.",
      "title": "Static first"
    },
    "site:tool-calling-ui-control#section-how-an-answer-reaches-the-page": {
      "citable": true,
      "entity": "site:tool-calling-ui-control",
      "kind": "free",
      "markdown": "One question is one `POST` to `/turn`. The answer streams back as newline-delimited JSON frames: text, sources, actions, tool progress and an end frame (ADR-0034). The browser gives up if the first frame takes more than 5 seconds, if frames stop for 10, or if the whole turn passes 30. A failure becomes one of a short list of fixed sentences, and the page around it is untouched.",
      "order": 3,
      "text": "One question is one POST to /turn. The answer streams back as newline-delimited JSON frames: text, sources, actions, tool progress and an end frame (ADR-0034). The browser gives up if the first frame takes more than 5 seconds, if frames stop for 10, or if the whole turn passes 30. A failure becomes one of a short list of fixed sentences, and the page around it is untouched.",
      "title": "How an answer reaches the page"
    },
    "site:tool-calling-ui-control#section-how-far-this-has-been-proved": {
      "citable": true,
      "entity": "site:tool-calling-ui-control",
      "kind": "free",
      "markdown": "- **Measured**: an answer cannot contain a link. It is a mechanical condition of the injection set, clean on one run per model.\n- **Measured**: the model cannot send, because `send_message` is in no tool list at any rung. The injection set's mechanical \"claimed action\" condition, where an answer says it did something it cannot do, was clean on one run per model.\n- **Designed**: every destination is checked against the route table on the server and again in the browser, and nothing navigates on its own.\n- **Designed**: the contact path reaches one mailbox, enforced by the platform. No mail has been sent through it yet.",
      "order": 4,
      "text": "Measured: an answer cannot contain a link. It is a mechanical condition of the injection set, clean on one run per model.\nMeasured: the model cannot send, because send_message is in no tool list at any rung. The injection set's mechanical \"claimed action\" condition, where an answer says it did something it cannot do, was clean on one run per model.\nDesigned: every destination is checked against the route table on the server and again in the browser, and nothing navigates on its own.\nDesigned: the contact path reaches one mailbox, enforced by the platform. No mail has been sent through it yet.",
      "title": "How far this has been proved"
    },
    "site:tool-calling-ui-control#section-seven-tools-in-three-classes": {
      "citable": true,
      "entity": "site:tool-calling-ui-control",
      "kind": "free",
      "markdown": "Every tool is defined once, as a schema that generates both the definition the model sees and the validation the server runs (ADR-0030).\n\n| Class | Tool | What it does |\n|---|---|---|\n| read | `get_facts` | defined, but not given to the model yet: its call cannot carry the ids it needs, and the corpus is already in its prompt |\n| read | `get_availability` | returns a three-valued status with the date it was confirmed |\n| read | `search_knowledge` | defined, but not given to the model: the whole corpus is already in its prompt |\n| ui | `show` | resolves a destination on this site |\n| ui | `compare` | resolves a comparison of two or three projects |\n| external | `start_contact_request` | returns a link to the contact form |\n| external | `send_message` | not callable by the model at all |\n\nEvery result has one shape: data, the source ids that back it, or an error from a closed list saying whether a retry could help. Every field a read tool returns has three states, a value, withheld or absent, so \"that part is not public\" and \"that is not recorded\" never collapse into one. A stale fact keeps its date.\n\nA turn may make at most four tool calls and five model calls in 30 seconds. A failed tool is retried once, and only if its error says a retry could differ. A tool is abandoned after 2 seconds. A model call is never retried, and a turn never retries itself (ADR-0041). A turn ends in exactly one of four ways: answered, out of budget, timed out or refused.\n\nThe tools run as plain functions inside the agent, not behind MCP (ADR-0031). The ui and external tools only mean something for the page and the person that asked, so they are never exported to any protocol, in any phase. The read tools could be exported one day, but an MCP server would have to do something the published `kb.json` cannot, since anyone can already download the whole corpus in one request. \"It would be a good demonstration\" is not that reason, and explaining why a standard was declined is the better demonstration.",
      "order": 0,
      "text": "Every tool is defined once, as a schema that generates both the definition the model sees and the validation the server runs (ADR-0030).\n\nClass Tool What it does\nread get_facts defined, but not given to the model yet: its call cannot carry the ids it needs, and the corpus is already in its prompt\nread get_availability returns a three-valued status with the date it was confirmed\nread search_knowledge defined, but not given to the model: the whole corpus is already in its prompt\nui show resolves a destination on this site\nui compare resolves a comparison of two or three projects\nexternal start_contact_request returns a link to the contact form\nexternal send_message not callable by the model at all\n\nEvery result has one shape: data, the source ids that back it, or an error from a closed list saying whether a retry could help. Every field a read tool returns has three states, a value, withheld or absent, so \"that part is not public\" and \"that is not recorded\" never collapse into one. A stale fact keeps its date.\n\nA turn may make at most four tool calls and five model calls in 30 seconds. A failed tool is retried once, and only if its error says a retry could differ. A tool is abandoned after 2 seconds. A model call is never retried, and a turn never retries itself (ADR-0041). A turn ends in exactly one of four ways: answered, out of budget, timed out or refused.\n\nThe tools run as plain functions inside the agent, not behind MCP (ADR-0031). The ui and external tools only mean something for the page and the person that asked, so they are never exported to any protocol, in any phase. The read tools could be exported one day, but an MCP server would have to do something the published kb.json cannot, since anyone can already download the whole corpus in one request. \"It would be a good demonstration\" is not that reason, and explaining why a standard was declined is the better demonstration.",
      "title": "Seven tools in three classes"
    },
    "site:tool-calling-ui-control#section-the-agent-proposes-and-you-decide": {
      "citable": true,
      "entity": "site:tool-calling-ui-control",
      "kind": "free",
      "markdown": "An action reaches your browser as one of two kinds: a destination or, later, a confirmation (ADR-0032). A destination carries the address to go to and the id of what it is about. The server checks the address against the site's route table and the id against the list of real ids before sending it. Your browser checks them again before showing it. An action that fails either check is dropped, and the answer carries on as text.\n\nThe rule for what may happen without a click fits in one sentence: an action applies itself only when you can undo it with no loss. Scrolling to a section on the page you are already reading, with the focus moved and a one-step undo, qualifies. That arrives when the assistant moves onto content pages. Navigating to another page does not qualify, so it is always offered as an ordinary link and nothing happens until you follow it. The agent never changes the layout and never writes to your address bar. A destination whose page has been retired is never offered.\n\nIn the first phase the assistant lives on one page, [/ask](/ask), so every destination is an offered link (ADR-0020). The answer text itself cannot contain a link (ADR-0042), so there is no way for a destination to reach you except through these checks. Resolving what `show` and `compare` return needs no model call, and the links placed next to a section never reach a model at all.",
      "order": 1,
      "text": "An action reaches your browser as one of two kinds: a destination or, later, a confirmation (ADR-0032). A destination carries the address to go to and the id of what it is about. The server checks the address against the site's route table and the id against the list of real ids before sending it. Your browser checks them again before showing it. An action that fails either check is dropped, and the answer carries on as text.\n\nThe rule for what may happen without a click fits in one sentence: an action applies itself only when you can undo it with no loss. Scrolling to a section on the page you are already reading, with the focus moved and a one-step undo, qualifies. That arrives when the assistant moves onto content pages. Navigating to another page does not qualify, so it is always offered as an ordinary link and nothing happens until you follow it. The agent never changes the layout and never writes to your address bar. A destination whose page has been retired is never offered.\n\nIn the first phase the assistant lives on one page, /ask, so every destination is an offered link (ADR-0020). The answer text itself cannot contain a link (ADR-0042), so there is no way for a destination to reach you except through these checks. Resolving what show and compare return needs no model call, and the links placed next to a section never reach a model at all.",
      "title": "The agent proposes and you decide"
    },
    "site:tool-calling-ui-control#section-the-model-cannot-send": {
      "citable": true,
      "entity": "site:tool-calling-ui-control",
      "kind": "free",
      "markdown": "`send_message` is in no tool list, at any level of the fallback ladder (ADR-0033). A capability the model does not hold needs no prompt to restrain it. When you want to get in touch, the model can call `start_contact_request`. Until the form moves into the assistant, that returns a link to [the contact form](/contact).\n\nLater the form opens inside the assistant, and the send becomes a server-side effect of a confirmation token that only your own submission carries. The token is single-use, tied to the conversation and valid for ten minutes. If it expires, nothing is sent. Every field starts empty. A version where the model drafted your message from the conversation was measured and failed a bar written before the run, so it was dropped (ADR-0065). The same endpoint serves the plain form, which works without JavaScript through a review page rendered on the server (ADR-0063).\n\nThe contact path can reach one mailbox, and that limit is the platform's, not only the code's. Mail goes through Cloudflare's `send_email` binding, which is configured with my verified address as its only destination, so it physically cannot write to anyone else (ADR-0074).",
      "order": 2,
      "text": "send_message is in no tool list, at any level of the fallback ladder (ADR-0033). A capability the model does not hold needs no prompt to restrain it. When you want to get in touch, the model can call start_contact_request. Until the form moves into the assistant, that returns a link to the contact form.\n\nLater the form opens inside the assistant, and the send becomes a server-side effect of a confirmation token that only your own submission carries. The token is single-use, tied to the conversation and valid for ten minutes. If it expires, nothing is sent. Every field starts empty. A version where the model drafted your message from the conversation was measured and failed a bar written before the run, so it was dropped (ADR-0065). The same endpoint serves the plain form, which works without JavaScript through a review page rendered on the server (ADR-0063).\n\nThe contact path can reach one mailbox, and that limit is the platform's, not only the code's. Mail goes through Cloudflare's send_email binding, which is configured with my verified address as its only destination, so it physically cannot write to anyone else (ADR-0074).",
      "title": "The model cannot send"
    }
  },
  "tombstones": []
}
