# DIN CTRL / StreamDIN: full text > Data Integrity Network: provenance and recall for agent work Source: https://dinctrl.com/ . Every page listed in https://dinctrl.com/llms.txt; the console page's interactive panels read a synthetic demo field and are not reproduced here. ## DIN: the AI work-of-record DIN is the system of record for AI work, for any agent. It captures what an AI agent did at the tool-call boundary, grades each claim as evidence-supported or asserted, and keeps that record on your infrastructure. The free build is one field, up to 3 people and 1 AI agent, no signup, no card; the self-hosted plans from Starter to Small Business are on sale, monthly. ### What is DIN? A log tells you the agent ran. It does not tell you whether its claims survived contact with the evidence. A transcript of a claim is still a claim, written in the same confident voice whether the work held or not. DIN keeps the grade: what was proved, what was only stated, and what was later contradicted. The record lives in a field: one canonical store per tenant, where records are placed by what they rest on rather than filed by date. It runs on a machine you control, and the field listens on your own machine only: agents on the same machine connect through the plugin or the CLI, cloud chat history comes in through import, and hosted access is set up with you. ### How does DIN work? Five steps, the same for every producer, whether the work came from a Claude Code session or a Codex rollout: 1. Captured at the tool-call boundary. Not a summary the agent wrote about itself: the actual calls, kept while they happen. 2. Certified, claim by claim. Every claim carries a verdict: evidence-supported, or asserted. 3. Placed, not filed. A record is put where it belongs by what it rests on and what it is about. 4. Read before the next build. The next agent starts knowing what the last one established, and which parts of it held. 5. Followed forward. Take any claim and see everything built on top of it, with the part resting on unverified claims marked out. ### How does DIN grade a claim? Two questions, asked separately and never merged into one badge: how a record was obtained, and what it turned out to be worth. How it was captured is one of receipted, logged, inferred or mixed. What it proved is one of proved, asserted or refuted. A refuted claim stays in the record, marked, rather than being quietly removed. An inferred record never renders as a receipted one, anywhere in the console, at any zoom. Where the record cannot settle a position on its own, a person rules, with a name and a date on the stamp. ### What does DIN cost? One meter: fields. A field is a store, a team, a project, a client: one container of records, opened by one token. You are not billed for volume, for seats, for storage or for inference: grading runs on inference you already have (your assistant CLI, your own API key or a local model), so there is no usage line from us. From DIN 1.0.39 the field count is enforced: creating a field past your plan's number is refused, with the plan, the number and the way up named, and fields you already have keep working. Client orgs (Agency: 5) and ops layers are enforced the same way, from the signed licence; people on each plan are shown, not enforced. The free build is one field, up to 3 people and 1 AI agent, with no signup and no card, and it is available to download today for Linux x86-64 (verified). macOS is available on request. History import (graded up to the Reader level, in a 40,000-character window), recall, the scoped brief, the local console and the dependency inventory are free. Live capture, every reading level and the whole-chat read, and the dependency watch's delivery are paid. Paid plans are priced by number of fields, in USD per month. Self-hosted: Starter $29 (6 fields), Freelancer $99 (15), Team $199 (30), Small Business $299 (90), Agency $399 (90 fields across up to 5 client orgs). Enterprise (180 fields and up) is a conversation, not a checkout. Hosted, where we run it: from $50 (Starter) to $599 (Agency). The self-hosted plans from Starter to Small Business are on sale, monthly, and the pricing page opens a checkout on Stripe's own payment page. Agency and hosted are set up with you: contact us from the pricing page. ### What can DIN read? DIN grades claims against the evidence that produced them, so the evidence must still exist. Nine sources import today: Claude Code, Codex, Gemini CLI, Qwen Code, the Cline family, claude-mem, Grok, ChatGPT (its data export), and Zep / Graphiti (through din-import-graphiti). A tenth, claude.ai with the Claude desktop chats, imports from the claude.ai data export (din import claude-ai): each conversation is kept, secrets scrubbed, and placed ungraded at no cost, and --grade grades it. Importing is not grading: grading runs on your own inference, on any of three paths: your assistant CLI (Claude Code or Codex), your own API key (Anthropic, OpenAI, or any OpenAI-compatible endpoint) or a local model (Ollama, vLLM, llama.cpp). Claude Code is the path DIN's grading was measured on; the Codex, key and local paths are built and tested on stand-ins, and none of them has been validated against a real vendor yet. On Codex or an OpenAI key, gpt-6-sol at medium effort reads at Reader on Free (din grade on --effort sets the effort; Analyst and up are paid). Grading on the Google Gemini CLI is turned off, because DIN cannot lock its tools down. The matrix at /compatibility says what works with each agent and source. Other tools that keep the original conversation (Letta, LangGraph, OpenAI Sessions, AWS AgentCore events, Azure Foundry conversations, Google Agent Engine, Supermemory, Khoj, Basic Memory, SpecStory) can be graded once a mapper for them ships. Tools that store only extracted facts cannot be graded, because the thing a grade would point at is gone. Live capture, a paid feature: the installer asks which agent to capture, Claude Code, Cursor, OpenCode or Codex (or takes --agent). Gemini CLI, Qwen, Cline and Grok history import. Recall into the agent reaches Claude Code, Cursor, OpenCode, Codex and Gemini CLI once wired; anywhere else it is din recall in a terminal, and any agent runtime can read the field over its HTTP API with the token, and a person can stamp a record. ### Frequently asked questions Q: Is DIN free? A: The free build is: one field, up to 3 people and 1 AI agent, with graded history import (up to the Reader level, in a 40,000-character window), recall, the scoped brief and the local dashboard, no signup and no card, running entirely on your own machine. Paid is the same download plus a key that turns on live capture, every reading level and the whole-chat read, several agents on one field, more fields, the dependency watch and the paid panels. What is on sale today is on the pricing page. Q: Where does my data live? A: On infrastructure you control: your laptop or your own box. The installer starts one server on loopback behind a token it mints on your machine, and the field listens on your own machine only: agents on it connect through the plugin or the CLI, and cloud chat history comes in through import. Grading runs on your own inference: your assistant CLI (Claude Code or Codex), your own API key (Anthropic, OpenAI, or any OpenAI-compatible endpoint) or a local model (Ollama, vLLM, llama.cpp); DIN never pays for or sees those calls. A free install never checks in. A paid key is verified when you run din activate, and the signed entitlement it fetches belongs to that install and lasts 14 days; a paid install checks in, with a random install id, when you run din activate --renew and at most once a day when its field or console starts (or with din autostart). Q: Which platforms does the free build run on? A: Linux x86-64, verified. macOS is available on request (write to support@dinctrl.com): it is not on the download page, and the Linux installer says so on a Mac rather than failing halfway through a copy. Q: Is DIN open source? A: Not yet. The Community Edition source is coming: the plumbing will be licensed Apache-2.0 when it is published; binaries today. Where its public repository is published, the Get DIN page links to it, and until then it shows no link. The compiled grading engine and the commercial services are proprietary. Q: Are the records in this demo real? A: No. The console is real and running, and every count, trust mark and flag is read live from a field. The records in that field are invented: Brindlewood Trading Co. is a fictional company, nothing here is anyone's real data, and the console is read-only. ## Pages - DIN: the AI work-of-record for agent work | DIN CTRL (https://dinctrl.com/): DIN captures what an AI agent did at the tool-call boundary, grades each claim as evidence-supported or asserted, and keeps the record on your infrastructure. - Get DIN: open source, free build, or paid | DIN CTRL (https://dinctrl.com/get): Three ways into one product: the open-source Community Edition (source coming), the free build with no signup and no card, or add fields on a paid plan. - Download the free DIN build for Linux | DIN CTRL (https://dinctrl.com/download): The free DIN build: one field, graded history import, no signup and no card, on your own machine. Linux x86-64 with signed checksums. - DIN pricing: one meter, fields | DIN CTRL (https://dinctrl.com/pricing): DIN is priced by one meter: fields. No charge for volume, seats, storage or inference. Free is one field, up to 3 people and 1 AI agent; paid adds fields. - DIN open source: the Community Edition | DIN CTRL (https://dinctrl.com/open-source): The DIN plumbing will be Apache-2.0 when its source is published; binaries today. Bring your own prompt. The grading engine is proprietary. - What DIN can read: compatibility | DIN CTRL (https://dinctrl.com/compatibility): DIN grades claims against the evidence behind them. Which agent tools keep the original conversation and can be graded, and which keep only facts. - DIN docs: how it works, the family, pricing | DIN CTRL (https://dinctrl.com/docs): The DIN docs index: how capture, grading and recall work, what each member of the DIN family does, what it costs, and the three ways to get it. - How DIN works: capture, grade, place, recall | DIN CTRL (https://dinctrl.com/docs/how): DIN is the record of what an AI agent actually did: captured at the tool-call boundary, graded claim by claim, and kept on infrastructure you control. - The honesty grading: how DIN grades a claim | DIN CTRL (https://dinctrl.com/docs/grading): Two questions, asked separately and never merged into one badge: how a DIN record was obtained, and what it turned out to be worth once checked. - The blast radius: what breaks if one thing is wrong | DIN CTRL (https://dinctrl.com/docs/blast): What breaks if one thing is wrong, crossed with how much of what it touches nobody ever verified. The trust-weighted blast radius in DIN, explained. - The graded brief: decided, unproven, contradicted | DIN CTRL (https://dinctrl.com/docs/brief): One question asked across the whole record, answered in three parts: what was decided, what is still unproven, and what has been contradicted. - The review queue and the human stamp | DIN CTRL (https://dinctrl.com/docs/review): The positions the DIN record cannot settle on its own, laid out with both sides, and the human stamp, with a name and a date, that settles one. - The field and the tree: placed, not filed | DIN CTRL (https://dinctrl.com/docs/field): One canonical store per tenant, where every DIN record is placed by what it rests on and what it is about, rather than filed away by date. - DIN CTRL: trust marks and change impact | DIN CTRL (https://dinctrl.com/docs/dinctrl): DIN CTRL shows how each record was captured and what it proved, and the trust-weighted blast radius of a change. The governed bus is on the roadmap. - RecordDIN: write it | DIN CTRL (https://dinctrl.com/docs/recorddin): The write side of DIN: sessions, source, code and commits, captured at the tool-call boundary and certified before anything is written. - FieldDIN: place it | DIN CTRL (https://dinctrl.com/docs/fielddin): FieldDIN is the field itself: one canonical store where every record of agent work is placed by what it rests on and what it is about. - RecallDIN: remember it | DIN CTRL (https://dinctrl.com/docs/recalldin): RecallDIN is the read side, in real time: what your company already established, put back into the agent run that is starting now. - StreamDIN: see it | DIN CTRL (https://dinctrl.com/docs/streamdin): StreamDIN is the review layer: every piece of AI work laid out as it actually happened, marked by what the evidence behind it supports. - UpstreamDIN: recover the past | DIN CTRL (https://dinctrl.com/docs/upstreamdin): UpstreamDIN is the one-time import that fills a DIN field with everything from before there was a record: existing chats, transcripts and files. - DownloadDIN: ask it | DIN CTRL (https://dinctrl.com/docs/downloaddin): DownloadDIN is the analyst: one question across the whole record, answered as a short graded brief in an hour rather than a week. - Install DIN: verify the download, then install | DIN CTRL (https://dinctrl.com/docs/install): Install the free DIN build: which platforms are supported, how to verify the download with the published minisign key, and what the installer does. - Activate a paid DIN licence: din activate | DIN CTRL (https://dinctrl.com/docs/activate): How din activate turns a paid licence key into a signed entitlement, online or offline with --file, what it writes, and how to renew it. - Console settings: activate, webhooks, capture, agents | DIN CTRL (https://dinctrl.com/docs/settings): Paste a licence key, manage webhooks, capture exclusions, autostart, agents and fields from the local DIN console, each by the din command it names. - Upgrade DIN to a new release | DIN CTRL (https://dinctrl.com/docs/upgrade): Upgrade DIN in place: stop the field, run the new release's installer, check it. Your records, field token and settings are kept. - Push your records to a hosted DIN field: din hosted | DIN CTRL (https://dinctrl.com/docs/hosted): How din hosted connects this machine to a hosted DIN console, pushes your records up and recalls them, and how agents and the dashboard sign in. - Use DIN as a team, self-hosted | DIN CTRL (https://dinctrl.com/docs/team): The self-hosted team setup that works today: one machine runs the field, teammates review over an SSH tunnel, Free is up to 3 people, team review adds more. - Any agent: read your DIN field with a token | DIN CTRL (https://dinctrl.com/docs/any-agent): Any agent runtime reads your self-hosted DIN field with a GET and a bearer token: recall, search, the brief, the network rules, and what was tested. - The DIN check on a GitHub pull request | DIN CTRL (https://dinctrl.com/docs/alm-github): din alm pr-check writes what your DIN field holds about a pull request onto it as one GitHub check run: sessions, claims, grades, neutral by default. - DIN plans: what each includes and what is enforced | DIN CTRL (https://dinctrl.com/docs/plans): Fields, ops layers and orgs for each DIN plan, what Free includes, what every paid plan adds, and which limits the programs enforce from your licence. - Billing, cancelling and refunds for DIN | DIN CTRL (https://dinctrl.com/docs/billing): Manage billing, a failed payment and its 7-day grace, cancelling at the end of the paid month, refunds, and what happens to your records: none is deleted. - DIN dependencies and the library catalog | DIN CTRL (https://dinctrl.com/docs/deps): The library inventory and the dependency watch (a paid feature), what each command sends and to whom, catalog-only enrichment, and the signed catalog's expiry. - DIN receipts: closed, unclosed and tampered | DIN CTRL (https://dinctrl.com/docs/receipts): What din-receipt-verify checks, what OK, OK-UNCLOSED (exit 3) and TAMPERED mean, and the options that relax or tighten the check of a receipts file. - DIN relay placement: other machines' records | DIN CTRL (https://dinctrl.com/docs/relay): How a field that receives runs through a relay places them: the relay's org node, inventories bound to their uploader, its receive time, and --relay-only. - DIN Agency: client orgs, set up with you | DIN CTRL (https://dinctrl.com/docs/agency): DIN Agency, set up with you: Small Business capacity across up to five isolated client orgs. What an org is, and how to keep clients apart in fields today. - DIN FAQ: frequently asked questions | DIN CTRL (https://dinctrl.com/docs/faq): Short answers about DIN: what it is, what is free, where your data lives, who pays for model calls, platforms, agents, licences, cancelling and refunds. - Troubleshooting DIN: the messages and what to do | DIN CTRL (https://dinctrl.com/docs/troubleshooting): The DIN messages you are most likely to meet when installing, running the field, activating a licence or checking dependencies, and what to do about each. - Your DIN data: what leaves, export, delete | DIN CTRL (https://dinctrl.com/docs/data): Where DIN keeps your records, the only things that send anything off your machine and when, how to export everything, and how to delete it yourself. - DIN security: how the record is protected | DIN CTRL (https://dinctrl.com/docs/security): Signed downloads, a field that answers to this machine only, signed licences, secrets redacted before anything is written, and how to report a vulnerability. - Uninstall DIN, and keep or remove your records | DIN CTRL (https://dinctrl.com/docs/uninstall): Remove DIN from a machine: stop the field, remove the plugin and the programs, and decide what to do with your records, which nothing deletes. - DIN command-line reference | DIN CTRL (https://dinctrl.com/docs/cli): The DIN command-line reference: the help text of din and every program in the free build, captured from the release's own programs. - DIN changelog: what changed in each release | DIN CTRL (https://dinctrl.com/docs/changelog): What changed in each published release of the free DIN build, newest first, stated from the release's own programs and shipped documents. - DIN for enterprise: a record your auditors can read | DIN CTRL (https://dinctrl.com/enterprise): DIN captures what your AI agents did at the tool-call boundary and grades every claim by how it was obtained and whether it held, on your infrastructure. - DIN for agencies: five clients, five walls | DIN CTRL (https://dinctrl.com/agency): DIN Agency, set up with you: the Small Business capacity split across up to five isolated orgs, one per client, managed from one install with din org. - DIN for small business: one company, one bill | DIN CTRL (https://dinctrl.com/smb): DIN for small business: one org and a field per team, project, store or client you want kept apart. Self-hosted, grading on your own inference. - For AI agents | DIN CTRL (https://dinctrl.com/for-agents): What DIN is, what an AI agent can do on dinctrl.com, and where the brand facts, free product, pricing and lead endpoint live as machine-readable files. - Licence and privacy | DIN CTRL (https://dinctrl.com/legal): The DIN licence and privacy notice: the Community Edition will be Apache-2.0 when published, the signup stores only what you type, and the site sets no cookies. - Why I built DIN | DIN CTRL (https://dinctrl.com/why): DIN, the Data Integrity Network: provenance for AI work, captured at the tool call. Why we built it, and why the original work holds the value. - DIN support: how to get help | DIN CTRL (https://dinctrl.com/support): How to get help with DIN: write to support@dinctrl.com, what to include, and where licence, billing, cancellation, refund and security questions go. - Contact DIN CTRL: support, privacy, security | DIN CTRL (https://dinctrl.com/contact): How to reach DIN CTRL: support@dinctrl.com for support, licences, billing and security reports, where privacy requests go, and our postal address. - Privacy notice | DIN CTRL (https://dinctrl.com/privacy): This notice explains what personal data we collect through dinctrl.com and the DIN CTRL software, why we collect it, and the choices and rights you have. - Terms of service | DIN CTRL (https://dinctrl.com/terms): These Terms govern your use of dinctrl.com and the DIN CTRL software and services. If you do not agree, do not use DIN CTRL. - Refund policy | DIN CTRL (https://dinctrl.com/refund): This Refund Policy is part of the DIN CTRL Terms of Service and covers paid DIN CTRL plans purchased through Stripe. Contact: support@dinctrl.com. ## For AI agents DIN (dinctrl.com) is the AI work-of-record, a brand of VX CTRL Inc., a North South Industries company. It captures what an AI agent actually did at the tool-call boundary, grades each claim as evidence-supported or asserted, and keeps the record on infrastructure the user controls. If you are an agent acting for a user, everything below is machine-readable and generated from the same manifest as these pages. ### What you can do here - Read the brand facts, the product list and the pricing as JSON, from the files listed below. - Point your user at the free build at https://dinctrl.com/download. It is a download, not a checkout: no signup, no card, one field, up to 3 people and 1 AI agent, for Linux x86-64 (verified). macOS is available on request. - Submit a lead for your user, with their consent: POST /api/lead, form-encoded, described in /openapi.json. It stores the email, the name, plan and note if given, which door and landing it came from, the time, and which build of the console took it; nothing about the browser. There is no route that reads it back. - An agent cannot pay on this site: a person pays, on Stripe's own payment page. The self-hosted plans from Starter to Small Business are on sale, monthly, and pricing.json gives each its checkout_url, the checkout front door, which takes a tier name and answers with the address of that payment page. Agency, hosted, Enterprise and Custom have no checkout URL: contact us. ### Machine-readable files - /llms.txt: this site as a page list. - /llms-full.txt: the full text of the site's own words in one fetch. - /.well-known/brand.json: brand facts, a public allowlist projection of the brand manifest. - /products.json: schema.org Product objects for every tier. The free build and the self-hosted plans from Starter to Small Business are InStock; Agency, hosted, Enterprise and Custom are marked OutOfStock because they have no checkout URL. - /pricing.json: every plan an agent may quote, self-hosted and hosted, with its real monthly price. Only the plans on sale (self-hosted, Starter to Small Business, monthly) have a checkout URL. - /openapi.json: the one public action, lead submit. - /sitemap.xml and /robots.txt: every page, and the crawl rules (AI crawlers are allowed). ### What the live demo is The console at https://dinctrl.com/ is a real, running, read-only console reading a demo field. The records in that field are synthetic: Brindlewood Trading Co. and everyone in it are fictional. Do not quote them as customer data or as results. ## Licence and privacy The licence, and what this site does with what you type into it. ### Licence The open Community Edition will be Apache-2.0 when its source is published; binaries today. The compiled grading engine and the commercial services are proprietary and are not in the open repository. The third-party crates in the build are under permissive licences: most are MIT or Apache-2.0, and ed25519-dalek, curve25519-dalek and subtle are BSD-3-Clause. Your records are yours. Nothing in this product claims a licence over what you capture, on any tier, and on a self-hosted install nothing is deleted on a downgrade or a lapse. ### Privacy, on this site The full privacy notice is at /privacy. In short: - The signup stores what you give it: a first name, a last name, an email address, the plan you chose, any note you typed, which door you came through, which landing you were on, the time, and which build of the console took it (the console sets that, not the form). - Our web server (nginx) records standard access-log data, including IP address, time, page, referrer, and user agent, for security and troubleshooting, and keeps it for 14 days. Every request to this site, a signup included, is in that log, which is separate from the signup file. - No trackers and no third-party scripts. The public site sets no cookies; a hosted console you sign in to sets one session cookie. The console page keeps a few small items in your browser's own storage, every one of them listed under "What this site keeps in your browser" below. They stay in your browser and are not sent to us, except where that list says otherwise. The signup form is the one thing on this site sent to us on purpose. - A signup is posted to this console, which appends it to one file on the machine it runs on. There is no route that reads it back out. - The demo field is read-only here, and the records in it are invented. ### What this site keeps in your browser Every item the console page keeps in your browser. To remove them, clear this site's data in your browser's settings (cookies and site data), or use a private window, which forgets them when it closes. Nothing on our side depends on them. - fielddin-theme (localStorage): light or dark, the theme you picked. Kept until you clear it. - din.demo.intro.v1 (localStorage and sessionStorage): 1, meaning you closed the welcome box on the demo, so it is not shown twice. The localStorage copy is kept until you clear it; the sessionStorage copy until the tab closes. - din.demo.hook.v1 (localStorage): 1, meaning you closed the follow-an-example banner on the demo. Kept until you clear it. - fielddin-gate-open (localStorage): 1, meaning you left a name and an email, so the sample's records open in this browser. It is not an account. Kept until you clear it; your name and email were sent to us with the form and stay on our list. - fielddin-free-look (localStorage): the ids of up to 3 records and a count of briefs, meaning which records and how many briefs you opened before the sample asks for an email, so a record you have seen opens again. Nothing is sent. Kept until you clear it. - fielddin-gate-dismissed (localStorage): how many times you closed the email form, per screen. It shortens the form's wording the second time and never unlocks anything. Kept until you clear it. - fielddin-who (localStorage): the identity you typed under Your own record, to fill the box in next time. The value is sent to the console when you ask for your numbers, as part of that request. Kept until you clear it. - __Host-din_hosted (cookie, HttpOnly): a signed expiry and a random session id. Only on a hosted console you sign in to, never on this public site. It is sent back to that console with each request, which is how it knows you signed in. Lasts 8 hours. ### Privacy, in the product What leaves your machine is listed in full in the privacy notice at /privacy. - Self-hosted. The installer starts one server on loopback behind a token it mints on your machine. A paid licence is verified when you run din activate: one call to our licensing service, or none on a machine with no network: din activate --file with a saved reply, which lasts 14 days too, so an offline install needs a fresh reply carried to it every 14 days. The programs then check its signature on your machine. A paid install checks in with api.dinctrl.com, with a random install id, when you run din activate --renew and at most once a day when the field or the console starts (or with din autostart); each signed check-in lasts 14 days. A free install never checks in. A key stays valid for up to 72 hours past each billing date. - Your inference is yours. Grading runs on your assistant CLI (Claude Code or Codex), your own API key (Anthropic, OpenAI, or any OpenAI-compatible endpoint) or a local model (Ollama, vLLM, llama.cpp), never on our account; DIN never pays for or sees those calls. The Codex, key and local paths are built and tested on stand-ins; none of them has been validated against a real vendor yet. - The capture records the model and a coarse mode label as provenance. Never the credential. ### Terms The terms of service that govern dinctrl.com and the DIN CTRL software are at /terms. ### Refunds The refund policy for paid DIN CTRL plans is at /refund. Source: https://dinctrl.com/why ## Why I built DIN I learned to code at 40, alongside AI agents. Every few weeks a new model arrived, an old one retired, and the same agent behaved differently from one version to the next. I came to accept that working on the cutting edge means you are part of the experiment: you are living in their sandbox, and paying for the privilege. By early 2026, every model nodded along. Anything seemed possible, and every change came back "done". Many of us worked in the chat window, copying code out of a conversation and pasting it into a terminal, trusting that the conversation would still be there when we needed it. It was, but nobody went back to it. The reasoning behind the code stayed in the chat, and only the code moved on. Others moved into the terminal early and built their own memory: prompts that made the agent stop and write handoff files, instructions to read the file tree before starting, and eventually loops that ran on their own. It felt like handoffs had been solved, because the next agent could read what the last one left. But an agent only reads what the last one wrote down, and a file is not memory. It does not know what was tried, what failed, or what was only assumed to work. Underneath all of it, the original conversations piled up, and almost nobody has gone back through them to see what was actually proven. And none of us stayed in one place. We moved between Claude, ChatGPT, Grok and open models, and then into the wave of self-hosted agents that run on their own. Every move left another history behind, in another format, with no shared record of what happened. So the assumptions piled up. Each new piece of work was built on the last one's word that it was done, and every echo that came back sounding new was carried forward with it. Before long, no one could say which parts of the project had ever actually been proven. Memory tools came and went, and each one stored something: saved chats, summaries, snapshots, running journals. We learned the hard way that the value is in the original work, meaning what the agent actually ran and what actually came back. A retelling of the work, however good, is not the work. Nobody was giving us provenance, so we built it. DIN records the work at the tool call, as it happens, and marks which claims a result actually backs. A claim that something is new, or that it works, gets the same mark as every other claim: backed by what ran, or only said. Then we went back through every conversation we had ever had and graded it the same way, so we could see the blast radius across our projects: if this changes, what breaks, and how much of it rests on claims nobody ever proved. This matters more every month. Agents now run headless, orchestrate other agents, and act on your behalf as personal assistants. When an agent's word is copied forward into the next agent's work, that word is the risk. Provenance is how you keep that risk accountable. That is what DIN stands for: the **Data Integrity Network**. We built it into a family of tools and pointed it at our own history first: every past conversation, and the work that came out of them. Today our agents don't start from a blank page or a handoff file. They work from the field, which captures each conversation as it happens, keeps the record honest in real time, and answers their questions with a receipt: the record and the exact passage the answer came from. Our agents work faster and more honestly because the data under them has integrity. What started as memory, and then provenance, has become a system of record: an account of what was done, by which agent, on what evidence. That record is worth more than the work of any single day. Every conversation you have had with an AI is inference you have already paid for: the reasoning, the dead ends, the decisions and why they were made. Most of it sits in old chats, unread. DIN treats that inference as what it is: intellectual property. It is yours to keep, to build on, and to stand behind when someone asks how your product was made. What we are giving you is the foundation: the bottom layer, the part everything else stands on. The record, the grades, the capture, the field. It is Apache-2.0 when the source is published; binaries today. Its source is coming, and once it is out you are welcome to fork it. We mean that. But model releases used to come with the seasons, and now they come with the moon. Every month there is a new one, and every month spent rebuilding the floor is a month spent not building on it. You can spend your own inference recreating what we have already worked through, or you can start from here. The foundation is free. The floors above it, like more agents on one field, more fields and the roll-up of your field's org tree, come with a key, on the same download, whenever you need them. We cannot wait to see what you build. We built DIN because we had no choice. Now it's yours. Source: https://dinctrl.com/support ## DIN support DIN CTRL support is one mailbox: [support@dinctrl.com](mailto:support@dinctrl.com). Free and paid users write to the same address, and a person reads every message and replies by email. Mail from DIN comes from billing@dinctrl.com; replies go to support@dinctrl.com. **What to expect.** We are a small team and answer in the order mail arrives. There is no guaranteed response time (no SLA) on any plan today. DIN runs on your own machine and keeps working without us, so nothing you capture waits on a reply. ### Before you write - **`din status`** names every program, says whether your field is up and whether your token opens it, and says what to type next. Inside Claude Code, `/din status` does the same for the plugin; in Cursor, OpenCode or any other agent, run `din status` in a terminal. - **The guides.** [Install](/docs/install), [Upgrade](/docs/upgrade) and [Uninstall](/docs/uninstall) are one page each, and the [command-line reference](/docs/cli) is every program's own help. ### What to include - The release: the output of `din --version`. - Your platform (Linux x86-64; macOS if you were sent the build on request) and how you installed (the one-line install or the archive). - What you ran, what you expected, and what happened: the exact command and its output, pasted as text. - The output of `din status`, and for a field that will not start, the last lines of `din field log -n 40`. - For a licence or billing question: the email address the plan was bought with. **Never send** a field token, an API key, a password or a whole licence key. We never need them, and no DIN program prints a token. Read what you paste first: command output and logs can name your projects and file paths, and you decide what leaves your machine. ### Licences, billing, cancelling and refunds - **Activating a licence.** [Activate a paid licence](/docs/activate) covers `din activate`, online and offline. If a key is refused, write to support@dinctrl.com from the email address it was bought with. - **Your account.** Your [account page](/account) on the customer portal has your licence key and the download, and its Manage billing button opens the Stripe customer portal, where you change your payment method and see your invoices. - **Cancelling.** Cancel from Manage billing on your account page, or email support@dinctrl.com from the address on your account. Your paid features stay on through the end of the month you have paid for, and cancelling deletes none of your records. The [refund policy](/refund) has the full terms. - **Refunds.** The [refund policy](/refund) says when a charge is refunded (in full, if you ask within 14 days of your first paid charge) and how to ask: email support@dinctrl.com from the address on your account. ### Privacy and security - **Privacy requests.** To access, correct or delete your personal data, write to [privacy@dinctrl.com](mailto:privacy@dinctrl.com), the address the [privacy notice](/privacy) names. - **Security reports.** Report a vulnerability to [support@dinctrl.com](mailto:support@dinctrl.com) with "Security" in the subject, the address [security.txt](/.well-known/security.txt) names. Include the release, the platform, the steps to reproduce and what an attacker would gain, and please give us the chance to ship a fix before you publish the details. [Contact](/contact) lists every address in one place. Source: https://dinctrl.com/contact ## Contact DIN CTRL DIN CTRL is a brand of VX CTRL Inc., a North South Industries company. A person reads every address below. There is no guaranteed response time (no SLA) on any plan today. - **Support, licences, billing, cancelling and refunds.** [support@dinctrl.com](mailto:support@dinctrl.com). [Support](/support) says what to include and where each kind of question goes. - **Security reports.** [support@dinctrl.com](mailto:support@dinctrl.com), with "Security" in the subject: the address [security.txt](/.well-known/security.txt) names. - **Privacy questions and data requests.** [privacy@dinctrl.com](mailto:privacy@dinctrl.com), the address the [privacy notice](/privacy) names. - **Enterprise, partners, press and everything else.** [support@dinctrl.com](mailto:support@dinctrl.com), with what it is about in the subject. - **By post.** VX CTRL Inc., 550 N 5th Street, Suite 112, Rapid City, SD 57701, USA, the address the [privacy notice](/privacy) gives. Free and paid users write to the same addresses. Your [account page](/account) on the customer portal has your licence key, the download and Manage billing. Source: https://dinctrl.com/privacy ## DIN CTRL Privacy Notice Last updated: October 26, 2026. DIN CTRL is a brand of, and owned by, VX CTRL Inc., a North South Industries company. This notice explains what personal data we collect through dinctrl.com and the DIN CTRL software, why we collect it, and the choices and rights you have. ### Who we are VX CTRL Inc., a South Dakota corporation, at 550 N 5th Street, Suite 112, Rapid City, SD 57701, USA, operating the DIN CTRL brand ("DIN CTRL", "we", "us"). For privacy questions and data requests: **privacy@dinctrl.com**. ### DIN is self-hosted DIN runs on your own machine. The field and console listen locally, and by default we host nothing and see nothing of your records. Your records stay with you. The only things that leave your machine are: - your imports and the "why" layer, which go to **your own model provider on your own key**; - licence check-ins to **api.dinctrl.com** carrying your licence key: when you run `din activate`, and, if you turn on `din autostart` on a paid plan, at login and once a day to renew it; - if you press Upgrade in your local console, your name, email address and chosen plan, sent from your browser to api.dinctrl.com to open a Stripe checkout; - hosted push, used only if you are a hosted customer; - any webhooks you configure; - on a paid plan, only if you switch on the dependency watch's scheduled check (`din deps refresh on`): a download of DIN's signed library catalog from **catalog.dinctrl.com**, which sees your IP address and which ecosystems (npm, cargo, PyPI and so on) you asked for. No package name, path, code or record is sent; - only if you opt in further: `din deps refresh --api` sends the ecosystem, name and exact version of each library in your inventory to DIN CTRL's catalog API at **catalog.dinctrl.com**; `DIN_DEPS_LIVE=on` or `DIN_DEPS_MODE=live` sends package names and versions to the public services **api.github.com** and **api.osv.dev**, and to the public registry of each ecosystem you use (registry.npmjs.org and api.npmjs.org, crates.io, pypi.org, proxy.golang.org, repo1.maven.org, rubygems.org, repo.packagist.org and packagist.org, api.nuget.org). It also fetches two public rankings, sent no package name: NuGet's from azuresearch-usnc.nuget.org and the top-pypi-packages list from hugovk.dev. That is every host it contacts. Never a path, code or record. The agent plugin in the DIN bundle sends nothing anywhere: it hands what it captures to the field on your own machine. An older Python plugin, retired on October 22, 2026 and no longer published, could upload runs to a DIN-run relay when it was installed with `--hub`; if you still have it, remove it. We never pay for, resell, or proxy model inference. ### What we collect - **Contact and signup requests:** first name, last name, email address, the plan you chose, any note you typed, which entry point you came through, which landing applied, and a timestamp. Used to contact you about availability and launch. - **Account and billing:** paid plans are handled by **Stripe**. We store your Stripe customer id, subscription id, your plan, and your licence. **Card data never touches our servers.** - **Licence activation and renewal:** activating paid features, and each renewal check-in, sends your licence key to api.dinctrl.com. It also sends your install id: a random number `din activate` makes once on your machine, which names no machine or person. We keep the install ids each licence checked in from with your licence, to see how many installs use it. Because that is a network request, our server also sees the originating IP address. - **Hosted service:** if you ask about hosted, we collect your contact details. - **Support:** what you send us when you contact us. - **Server logs:** our web server (nginx) records standard access-log data, including IP address, time, page, referrer, and user agent, for security and troubleshooting. ### Cookies and browser storage The public site sets **no cookies**, and the site and console use **no third-party trackers, no analytics, and no browser fingerprinting**, and load no external scripts. The customer portal (app.dinctrl.com) sets **one session cookie**, `__Host-din_portal`, when you sign in with an emailed link: it lasts 24 hours, is HttpOnly, Secure and SameSite=Lax, holds a random session token and nothing about you, and signing out ends it. A hosted console sets one session cookie of the same kind when you sign in. Both are strictly necessary for the sign-in, so no cookie banner is required. Browser storage is listed item by item on [/legal](/legal); none of it is sent to us except as /legal describes. ### Why we process it, and our legal bases (GDPR / UK GDPR) - Creating and managing your account and licence: performance of a contract. - Contact and signup requests, and launch or marketing email: your consent. - Validating licences and securing the service (including server logs): our legitimate interests. - Taking payment and meeting tax duties: contract and legal obligation. - Responding to support: legitimate interests. ### Sharing and subprocessors We do not sell your personal data and do not share it for advertising. We use: **Stripe** (payments and subscriptions), **IONOS** (hosting for the site, console assets, and the billing API), our **own mail relay (mail.cmdpath.com)** for transactional email, and **self-operated DNS**. We may disclose data to comply with law or in a merger, with notice where required. ### International transfers We are based in the United States and process data there. Where we transfer personal data from the European Economic Area or the United Kingdom, we rely on appropriate safeguards, including the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum. ### Retention What is kept, and for how long: - Billing records: Stripe keeps invoices and payment records for 7 years, for tax. We keep our record of each billing email (licence key, plan changes, payment notices, refunds, disputes) and the address it went to with your account, as part of that billing record. - Sign-in links and other email that is not a billing record (security and dependency alerts, digests): deleted 14 days after it was sent, by the mail service's own run. - Mail logs: our mail service never writes a full recipient address to its log; it writes a masked one (the first letter and the domain). - Licence records: for the life of the licence plus 12 months. A monthly purge then tombstones the record: your email address and licence key are deleted, and only the account and Stripe ids, plan and dates are kept. - Contact and signup requests: until you ask to be removed (email privacy@dinctrl.com and we delete them). Otherwise a daily purge removes them once they are 24 months old. - The portal session: 24 hours, or until you sign out. An emailed sign-in link works once, within 20 minutes. - Server logs: 14 days. - Your own records live on your own machine and are not deleted by us on a downgrade or a lapse. ### Your rights Depending on where you live, you may have the right to access, correct, delete, restrict, or object to processing, to data portability, and to withdraw consent, and to complain to a supervisory authority (in the EEA/UK) or your state regulator. **California residents (CCPA/CPRA):** you have the rights to know, access, correct, and delete your personal information, and to limit the use of sensitive personal information; we do not sell or share personal information for cross-context behavioral advertising. To exercise any right, email **privacy@dinctrl.com**; we respond within the time the law requires. ### Children DIN CTRL is not directed to children under 16, and we do not knowingly collect their personal data. ### Changes and contact We will post any update here with a new date. VX CTRL Inc., 550 N 5th Street, Suite 112, Rapid City, SD 57701, USA. Contact: privacy@dinctrl.com. Source: https://dinctrl.com/terms ## DIN CTRL Terms of Service Last updated: October 31, 2026. ### 1. Agreement DIN CTRL is a brand of, and owned by, VX CTRL Inc., a North South Industries company (VX CTRL Inc., a South Dakota corporation, 550 N 5th Street, Suite 112, Rapid City, SD 57701) ("DIN CTRL", "we", "us"). These Terms govern your use of dinctrl.com and the DIN CTRL software and services. By downloading, activating, or using DIN CTRL, you agree to these Terms, the Privacy Notice, and the Refund Policy. If you are acting for an organization, you confirm you have authority to bind it. If you do not agree, do not use DIN CTRL. ### 2. The free download The free DIN CTRL build is a download. Its open plumbing will be licensed under the **Apache License, Version 2.0** when its source is published; until then, and for its closed components, the free build is licensed under the terms included with the bundle. Your use of the free build is governed by those licences. ### 3. Paid plans and licence Paid features are turned on in the same binary by a licence key. **Paid plans are monthly subscriptions, billed through Stripe (no annual option).** Your licence lets you and your named affiliates use the paid features within your plan's limits. The licence is for you; do not share, resell, or sublicense it, and do not circumvent licence or security features. The detailed paid-component licence terms are provided with the bundle. ### 4. Licence activation Activating paid features sends your licence key to api.dinctrl.com, as described in the Privacy Notice. Nothing else about your machine or your records is sent as part of activation. ### 5. Hosted service A hosted version of DIN CTRL is set up with you on request. It has its own terms and, for business customers, a data processing addendum. ### 6. Your data and ownership DIN is self-hosted: your records stay on your own machine and we do not receive them by default. As between us, you own your content, and we claim no licence over it. See the Privacy Notice for the limited data we do process. ### 7. Billing, renewal, and taxes Monthly subscriptions renew automatically at the then-current price until you cancel, and you authorize the recurring charge through Stripe. Prices exclude taxes, which may be added at checkout. Cancellation and refunds are governed by the Refund Policy. **Failed payments.** If a renewal payment fails, Stripe retries the card and your paid features continue for a grace period of **7 days** from the first failure; the email we send names the date. Paying at any point during the grace period restores normal billing. If the payment is still unpaid when the grace period ends, the licence ends and your install moves to the free tier at its next check-in. Separately, a licence key stays valid for up to 72 hours past each billing date, so that a renewal has time to reach your install. **Payment disputes.** A bank's request for information about a charge (an inquiry) suspends nothing. A chargeback suspends your paid features while it is open: the licence is ended at once and your install moves to the free tier at its next check-in. If the chargeback is decided in our favour, the licence is restored; if it is decided against us, the licence stays ended and the subscription is cancelled, so you are not charged again. We email you when a chargeback is opened and when it is decided. Please contact support@dinctrl.com before disputing a charge: we would rather fix it with you. ### 8. Acceptable use You will not use DIN CTRL to violate any law or third party's rights, upload malware, attempt to breach security, circumvent licensing or metering, resell the software as a service, or import or process data you do not have the right to import or process. ### 9. Intellectual property We and our licensors own DIN CTRL and the DIN CTRL name and logos, except your content and the open-source components, which remain under their own licences. ### 10. Disclaimers DIN CTRL is provided "AS IS" and "AS AVAILABLE" without warranties of any kind to the maximum extent permitted by law, including merchantability, fitness for a particular purpose, and non-infringement. DIN grades and briefs are informational aids about your own work records and are not professional, legal, or financial advice. ### 11. Limitation of liability To the maximum extent permitted by law, we are not liable for indirect, incidental, special, or consequential damages, and our total liability will not exceed the greater of the amount you paid us in the 12 months before the claim or USD 100. Nothing limits liability that cannot be limited by law; consumers may have additional non-waivable rights. ### 12. Term and termination These Terms apply while you use DIN CTRL. On a lapse, a downgrade, a refund of your first charge, an unpaid renewal after its grace period, or a chargeback (Section 7), paid features revert to the free tier and your data is not deleted. We may suspend or terminate access for material breach. ### 13. Changes, governing law, and contact We may update these Terms and will post the current version with a new date. These Terms are governed by the laws of the State of South Dakota, and the state and federal courts located in South Dakota have exclusive jurisdiction over any dispute. Contact: privacy@dinctrl.com. Source: https://dinctrl.com/refund ## DIN CTRL Refund Policy Last updated: October 23, 2026. This Refund Policy is part of the DIN CTRL Terms of Service and covers paid DIN CTRL plans purchased through Stripe. DIN CTRL is a brand of VX CTRL Inc., a North South Industries company. ### 1. Free download The free DIN CTRL build requires no payment and is not charged. This policy does not apply to it. ### 2. Subscriptions and auto-renewal Paid plans are **monthly subscriptions**. They renew automatically at the end of each month at the then-current price until you cancel, and you authorize the recurring charge at checkout. We will give advance notice of any price increase. ### 3. How to cancel, and failed payments You can cancel at any time through the Stripe customer portal or by emailing **support@dinctrl.com**. Cancellation stops future renewals; your paid features remain active through the end of the month you have already paid for; you are not billed again after cancelling. If a renewal payment fails, your paid features continue for a 7-day grace period while Stripe retries the card (Terms, Section 7). If it is still unpaid at the end of the grace period, the licence ends and your install moves to the free tier at its next check-in. ### 4. Refunds - **14-day money-back on your first paid charge:** if DIN CTRL is not right for you, request a refund within 14 days of your first paid charge for a full refund. **A full refund of the first charge ends the licence and cancels the subscription:** you are not charged again, and your install moves to the free tier at its next check-in. - **Renewal charges are generally non-refundable.** When you cancel, you keep access through the end of the month you paid for, and we do not pro-rate the unused part of that month unless the law requires it. ### 5. Consumer withdrawal (EU / UK) If you buy as a consumer in the EU, UK, or another jurisdiction with a statutory cooling-off period (typically 14 days), you may have a right to withdraw. If you ask us to begin providing paid features during that period, you may lose or limit that right once you have given informed consent to immediate performance. These statutory rights are in addition to Section 4. ### 6. Your data is not deleted Cancelling, downgrading, or letting a plan lapse does not delete your records; they remain on your own machine. ### 7. How to request, taxes, and chargebacks Request a refund by emailing support@dinctrl.com from the address on your account. Approved refunds are issued to your original payment method through Stripe; the time to appear depends on your bank. Prices exclude taxes, which may be added at checkout; refunds include any tax we actually collected. Please contact us before starting a chargeback, so we can resolve the issue directly. A chargeback suspends your paid features while it is open, and one decided against us ends the licence and cancels the subscription; a bank's inquiry suspends nothing (Terms, Section 7). ### 8. Changes and contact We may update this policy prospectively; the version in effect at the time of your charge governs it. Contact: support@dinctrl.com. Source: https://dinctrl.com/docs/install ## Install DIN The free build is one download: sixteen programs, the plugin and an installer. No account, no signup and no card. This page covers release 1.0.43. ### Which platforms - **Linux x86-64: supported.** This is the platform the release is built and checked on. - **macOS: available on request.** It is not on the download page: write to support@dinctrl.com. The Linux installer says so on a Mac and stops, rather than failing halfway through a copy. ### The one line ```bash curl -fsSL https://dinctrl.com/install | sh ``` That is steps 1 to 3 below, done for you, and it checks before it runs anything: 1. It refuses anything but Linux x86-64 by name, and a Mac unless the release carries a macOS build (on a Mac: "DIN for macOS is available on request: this release has no macOS download"). 2. It reads `SHA256SUMS` from the [download page](/download)'s own directory. The archive's name, and so the version, comes from that list. 3. It checks `SHA256SUMS.minisig` against the key printed below, which is written into the script and never fetched: with `minisign` when it is installed, otherwise with OpenSSL 3 or later, which most Linux machines already have. With neither, it stops and installs nothing: it prints "SIGNATURE NOT CHECKED, so nothing was installed" and names the two ways out, install minisign or run it on a machine with OpenSSL 3 or later. 4. It downloads the archive and stops unless its SHA-256 matches `SHA256SUMS`. 5. It unpacks the archive into a temporary directory and runs its `install.sh`, at your terminal, so the agent question below is still asked. Any mismatch: it deletes the temporary directory, installs nothing, and exits non-zero. It never uses sudo. You can read it first: open [dinctrl.com/install](https://dinctrl.com/install) in a browser. Every installer option works from the one line, after `sh -s --`: ```bash curl -fsSL https://dinctrl.com/install | sh -s -- --agent cursor curl -fsSL https://dinctrl.com/install | sh -s -- --prefix /opt/din --no-start curl -fsSL https://dinctrl.com/install | sh -s -- --path ``` `--path` is the one-liner's own option: it adds `export PATH="/bin:$PATH"` to your shell's profile (`~/.bashrc`, `~/.zshrc` or `~/.profile`). Without it, nothing is edited and the line is printed for you to run. Or do it by hand, reading the archive before you run anything: ### 1. Download Everything is on the [download page](/download). These are the release files: - [din-1.0.43-linux-x86_64.tar.gz](/download/din-1.0.43-linux-x86_64.tar.gz): the Linux x86-64 build - [SHA256SUMS](/download/SHA256SUMS): the SHA-256 of the release archive and producer-allow.txt - [SHA256SUMS.minisig](/download/SHA256SUMS.minisig): the minisign signature over SHA256SUMS - [minisign.pub](/download/minisign.pub): the public key SHA256SUMS is signed with - [producer-allow.txt](/download/producer-allow.txt): the sha256 of this release's din-record, din-session-record and din-import, the three producers a re-grade may come from (the copy the archive installs) From a shell: ```bash curl -fsSLO https://dinctrl.com/download/din-1.0.43-linux-x86_64.tar.gz curl -fsSLO https://dinctrl.com/download/SHA256SUMS curl -fsSLO https://dinctrl.com/download/SHA256SUMS.minisig ``` ### 2. Verify the download Every release is signed with [minisign](https://jedisct1.github.io/minisign/). The public key (key id `36C9AB1B4CC4A458`) is printed here, not only shipped beside the download it vouches for: ``` RWRYpMRMG6vJNhzPUkYbbwTX9ebqgd1rW50Rlkv+/BZ4uAPzfda0KTqK ``` ```bash # install minisign first: apt install minisign / brew install minisign minisign -Vm SHA256SUMS -P RWRYpMRMG6vJNhzPUkYbbwTX9ebqgd1rW50Rlkv+/BZ4uAPzfda0KTqK # -> Signature and comment signature verified # -> Trusted comment: DIN 1.0.43 (it names the version you downloaded; check it does) sha256sum --ignore-missing -c SHA256SUMS # -> din-1.0.43-linux-x86_64.tar.gz: OK ``` If either check fails, stop: do not run the installer. The installer does not check the signature for you. It checks only that the nine core programs and `din-grade` are present before it writes anything. ### 3. Install on Linux ```bash tar xzf din-1.0.43-linux-x86_64.tar.gz && cd din-1.0.43 sh install.sh export PATH="$HOME/din/bin:$PATH" din status ``` `din status` is the check that matters. It names every program, says whether the field is up, says whether your token opens it, and tells you what to type next. ### Pick your agent DIN is for any agent: any agent runtime can read the field through its HTTP API with the field token, and a person can stamp a record. The installer wires the agents it knows. Run at a terminal, it asks which agent DIN should capture: Claude Code, Cursor, OpenCode or Codex, one or several, Gemini CLI for recall only, or **6, none: import only** (ChatGPT and others, which have no live capture). Or say it up front with `--agent`, once per agent; `--agent none` is import only. With no `--agent` and no terminal (a script, a pipe) it picks the agent a person would have been offered, the first one it finds here (Claude Code when `claude` is on PATH, else Cursor, else OpenCode), and says which and why in its closing lines. With none of them here it wires none. - **Live capture:** Claude Code, Cursor, OpenCode and Codex. Live capture is a paid feature, and so are several agents on one field at once; history import is free, graded up to the Reader level in the fixed 40,000-character window. - **Recall:** Claude Code, Cursor, OpenCode, Codex and Gemini CLI, once wired. - **Import-only:** Gemini CLI, Qwen, Cline and Grok history, and Codex's past sessions, are read by `din import --source `. `--agent gemini` wires recall only and tells you that command. - **Graphiti and Zep:** read by `din-import-graphiti`, from a Graphiti or Zep endpoint you run. - **ChatGPT:** import-only, from its data export. In ChatGPT: Settings, Data controls, Export data; download the zip from the email, then `din import --source chatgpt --export `. `--agent chatgpt` installs DIN, wires nothing live, and tells you that command. Graded inferred, because the export carries no tool results to check, on whichever grading path you set up (below). - **claude.ai and the Claude desktop app's chats:** import-only, from the claude.ai data export. On claude.ai: Settings, Privacy, Export data (the desktop app's chats are the same account, so they are in it); then `din import claude-ai `. Each conversation is kept in `~/.din/vault/claude-ai/` (secrets scrubbed by default), and importing the same export again changes nothing. Records are placed ungraded, with no model call and no cost; `--grade` grades them, on any plan, Free included, as inferred, on your own inference. Pick several on the free build and each is still wired, but the field serves one AI agent: the newest, with the others set aside and kept in full. The installer says so in one line. `din field activate ` switches which one is served; a paid plan keeps them all live together, with live capture. To change your mind after the install, there is no need to run the installer again: ```bash din agent list # which agents are wired, and which one your field serves din agent add cursor # wire claude-code, cursor, opencode, codex or gemini din agent remove cursor # unwire it; its records stay in your field ``` On the free build, `din agent add` first says what a second agent does and, at a terminal, asks before it wires anything (`--yes` to skip the question). With no terminal to ask at (a script, or the console's Settings page with its box unticked), it wires nothing unless you pass `--yes`. The installer takes these options: ``` sh install.sh install into ~/din and bring it up sh install.sh --agent cursor which agent to capture (repeat for several): claude-code, cursor, opencode (live capture, paid); codex (recall; live capture, paid); gemini (recall; history by import); chatgpt, qwen, cline, grok, zep, graphiti, none (import only: nothing is wired) sh install.sh --grade-with key how grading runs: cli, codex, key or local (--grade-model M, --grade-url URL) sh install.sh --prefix /opt/din somewhere else sh install.sh --dry-run print every step, touch nothing sh install.sh --no-plugin skip the plugin: no agent is wired sh install.sh --no-start lay it down but do not start the field sh install.sh --port 8093 the field's loopback port sh install.sh --console-port 8097 the local console's loopback port sh install.sh --schedule also schedule the capture sweep (cron) ``` ### More than one field New in 1.0.32. One install can hold several fields, for example one per client or per project. Each has its own store, its own token (mode 600, never printed) and its own loopback port; they share this install's programs and your plan, and each starts on first use like your main one, which is called `main`. ```bash din field new work # ~/din/fields/work, on a free port (or --port N) din field list # every field: port, records, active agent, "N of M" on your plan din field use work # the default for recall, query, brief, console and import din recall --field work "" # --field picks one field for status, console, import, recall, # query, brief, where, dep-audit and din field start|stop|status ``` Your plan includes a number of fields, and `din field list` shows how many you have of that number. From 1.0.39 that number is enforced: past it, `din field new` (and `din field routes --import-capture-map --create`, and the console's Fields control) makes nothing, says your plan, how many fields it includes and how to get more, and exits 3. Free includes 1 field, your own `main`, so on Free `din field new` refuses; on Free up to 3 people review that field. The fields you already have are never touched: an install with more than its plan includes (made before 1.0.39, or kept after a downgrade) keeps every field working, and `din field list` says `OVER PLAN`. To have captures land in the right field, route each project to it. The plugin reads the routes at the end of each session and places that session's records into its project's field: ```bash din field route my-repo work # sessions in that project go to `work` din field route --default main # every project with no route of its own din field routes # what is routed where din field unroute my-repo ``` A project is matched, ignoring case, by the folder you work in (or `DIN_CHANNEL`), its name in `DIN_PROJECT_MAP` if you use one, or Claude Code's own name for the folder. With no routes at all, everything goes to your main field, as before. `din status` and `/din status` show each field and its last capture. If you kept a hand-written `capture-map.json`, `din field routes --import-capture-map ` shows what it would route, and `--create` also makes the fields it names. You can also make fields from the console: see [Console settings](/docs/settings). Routes apply to everything that captures on this machine: the plugin's hooks and sweep, the Codex sweep, and `din capture`. If a route names a field whose store is not there, nothing is placed, in that field or any other. The log says why, and the run is placed on a later pass once the store is back. A field can belong to another install on the same machine, for example a server with one install per field. Attach it by its store, then route to it. Its port and token file are recorded for `din status` and `din field routes`; the token file is never read, and nothing of that install is started or changed. An attached field counts as one of your plan's fields. ```bash din field attach core2 --store /srv/core2/records --port 8301 --token-file /srv/core2/.din/field.token din field route --default core2 # captures from this machine go to core2 din field detach core2 # after removing the routes to it; the store is untouched ``` On a server, a timer can feed one field with no capture map. Live capture needs a paid plan. ```bash din capture --once --field=core2 --skip-headless # one pass din capture install-task --field=core2 --skip-headless # every 10 minutes ``` `--field ` and `--field=` are the same flag. A project with a route of its own still goes to its route. With no capture map, the pass reads every project your `din capture exclude` and `din capture only` settings allow, and `din capture off` stops it. It starts from now: sessions already on disk are left alone unless you add `--backlog`. `--skip-headless` leaves out `claude -p` and SDK sessions, and applies to `din capture` only: to keep such sessions out of the plugin's hooks and sweep, exclude their folders with `din capture exclude `. An exclusion also covers folders whose name only begins the same way, so excluding `/srv/work` skips `/srv/work-2` too. Run either this timer or the plugin's sweep on a machine, not both, or a session is captured twice. `--skip-headless` leaves out `claude -p` and SDK sessions, and it is off by default. It is for a box where people work and spins run beside them. On a box where all the work is headless (supervisor mode), do not turn it on: it would leave out everything. Exclude only the directories you do not want captured, for example `din capture exclude ~/agent-runs`. ### What the installer does - On an upgrade, if the field from the same install is running, stops it with `din field stop` first. If it does not stop, nothing is replaced. - Copies the sixteen programs into `~/din/bin` (among them `din-session-record`, the producer `din capture` runs; `din-grade`, the grader `din-import` hands every grading command to; `din-import-graphiti`, `din-libcatalog`, `din-regrade`, `din-source`, `din-referee` and `din-autoingest` only when the download carries them, as this release's archive does; `din-autoingest`, the ingest watcher each `din-ingest@` instance runs, is in the Linux and macOS downloads only), and links `din-recall` to `din` (the name the plugin's `/din recall` looks for). - Puts `producer-allow.txt` beside the programs: the sha256 of the three producers a re-grade may come from, `din-record`, `din-session-record` and `din-import`. `dinctrl-store ingest --regrade` refuses a replacement from any other. - Copies `LICENSE`, `NOTICE` and `THIRD-PARTY-LICENSES` into `~/din/share/doc/din`. - Creates `~/din/records` (your records), `~/din/.din` (settings) and `~/din/logs`. - Mints a field token into `~/din/.din/field.token`, mode 600. No DIN program ever prints it. An existing token is never overwritten. - Writes `~/din/.din/field.env` with the field on `127.0.0.1:8093` and the console on `127.0.0.1:8097`. An existing file is left alone. - Writes the plugin's settings to `~/.din/plugin.env`, pointing it at this install. An existing file is left alone. - Starts the field on loopback with `din field start` and waits for it. - Wires the plugin into the agent you picked: Claude Code through its plugin installer, Cursor through its `hooks.json`, OpenCode through its plugin directory. With import only, nothing is wired and no sweep is scheduled. ### How grading runs: your own inference Nothing in the install needs an API key, and DIN never pays for, proxies or sees a model call. Three steps call a model, each on your own inference and each forecasting its cost first: `din import --grade`, `din grade on` (which grades live-captured sessions, so it needs live capture, a paid feature) and `din regrade --run`. None needs a spend cap; a cap you set (for example `din grade on --daily-cap USD`) holds, with one exception: on a model no price card covers, on a path that may bill per call (an OpenAI key, for one), a dollar cap cannot count, so it is not used and grading is held to 3 attempts a day instead. The installer asks how to grade (or say it with `--grade-with cli|codex|key|local`, and `--grade-model M`, `--grade-url URL`), and `din setup model` changes it later. There are three ways: - **Your assistant CLI, signed in:** Claude Code (`claude`) or Codex (`codex`, on your ChatGPT plan). Nothing is stored. Inside a subscription it uses your plan's limits. - **Your own API key:** Anthropic, OpenAI, or any OpenAI-compatible endpoint (`din setup model --key`, with `--base-url URL` for an endpoint). The key is stored on this machine in `$DIN_HOME/model-keys.env`, readable only by you, is never on a command line, and goes only to that vendor's host. - **A local model:** Ollama, vLLM or llama.cpp on this machine (`din setup model --local [URL] --model M`). Nothing leaves the machine. With more than one here, the order is the CLI (Claude Code first, then Codex), then a key, then a local model; `din grade on --via cli|codex|key|local` picks one. Claude Code is the path DIN's grading was measured on. The Codex, API-key and local-model paths are built and tested against stand-ins; none of them has been validated against a real vendor yet. Where a grading call goes is set in `~/.din/plugin.env`, not by your agent session's environment, because a repository's `.claude/settings.json` `env` block reaches the hooks: the proxy and CA settings (`HTTP_PROXY`, `HTTPS_PROXY`, `ALL_PROXY`, `NO_PROXY`, `SSL_CERT_FILE`, `SSL_CERT_DIR`, `CURL_CA_BUNDLE`, `NODE_EXTRA_CA_CERTS`), `ANTHROPIC_BASE_URL`, `CLAUDE_CODE_USE_BEDROCK` and `CLAUDE_CODE_USE_VERTEX`, `CLAUDE_CONFIG_DIR`, `CODEX_HOME` and `XDG_CONFIG_HOME`; so are where capture reads (`DIN_TRANSCRIPTS`) and your licence file (`DIN_ENTITLEMENT`). The plugin installer copies the proxy, the CA, `CLAUDE_CONFIG_DIR`, `CODEX_HOME` and `XDG_CONFIG_HOME` from the shell it runs in (only names plugin.env does not hold yet), and `din setup model` copies the proxy and CA. Otherwise put one there yourself, or put `DIN_TRUST_ENV=1` in plugin.env to let the environment set them. On Codex or an OpenAI key, a level depends on the model and its reasoning effort: `din grade on --effort ` sets it (every path runs at medium otherwise), and OpenAI levels above medium need it. gpt-6-sol at medium effort reads at Reader on any plan, Free included; Analyst and up are paid. DIN picks no model for you on Codex: name one. Grading on the Gemini CLI is turned off: DIN cannot run it with its tools locked down. A paid install also checks in with our licensing service, with its random install id: when you run `din activate`, at most once a day when the field or the console starts, and daily from its timer once you turn on `din autostart on`. Each signed check-in lasts 14 days. A free install never checks in. ### Next - [Activate a paid licence](/docs/activate), if you have one. The free build needs no activation. - [Console settings](/docs/settings): activate a key, webhooks, capture, agents and fields from the local console. - [Upgrade](/docs/upgrade) to a later release. - [Uninstall](/docs/uninstall), and what happens to your records. - [Push your records to a hosted field](/docs/hosted), if you have a hosted plan. - [The command-line reference](/docs/cli). Source: https://dinctrl.com/docs/activate ## Activate a paid licence `din activate` turns a paid licence key into the signed entitlement file that the field, the console and the plugin read. The free build needs none of this: with no entitlement file an install runs as the free tier. The self-hosted plans from Starter to Small Business are on sale, monthly, from the pricing page, and each comes with a licence key, read from your account area after checkout. This page documents the command as it is in 1.0.43, this release. A free install never checks in. A paid install checks in with our licensing service (`api.dinctrl.com`) with its random install id: when you run `din activate` or `--renew`, and on its own at most once a day when the field or the console starts (or with `din autostart on`). Each signed check-in lasts 14 days. ### Online ```bash din activate din activate - # the key read from stdin, so it stays out of your shell history din activate # re-activate with the key already saved in license.key ``` This needs `curl`. `din activate` checks the key in with the issuer (by default `https://api.dinctrl.com`, changed with `--url ` or `DIN_BILLING_URL`) and receives a signed entitlement in reply. The key is handed to `curl` on stdin, never on its command line, so it does not show in a process listing. ### Or paste your key in Plan No terminal needed. In the local console (`din console`), open **Plan and billing**, paste your key into **Activate a key** and press **Activate**. The console runs the installed `din activate -` on this machine with your key on its standard input, so the key is never on a command line and never in the console's log, and it shows what came back: your tier, what it turns on and when the current period ends, or the error `din` gave. The plan on that screen updates straight away, without a restart. The box is on the local console only, and it is new in 1.0.32: on an earlier release use `din activate -` in a terminal. The public demo and a hosted console do not have it. Every other setting the console can change is described in [Console settings](/docs/settings). ### Offline ```bash din activate --file ``` No network and no `curl`. The file is either the saved reply of a check-in (the JSON that `POST /api/license/verify` answered) or a bare signed envelope. On a machine that does have a network, the check-in `din activate` makes is: ```bash printf '{"key":"%s","install_id":"%s"}' '' '' | curl -sS -X POST -H 'content-type: application/json' --data-binary @- https://api.dinctrl.com/api/license/verify > reply.json ``` `` is the offline box's own id, from its `~/.din/install-id` (see **Your install id** below). `din activate --file` creates it if it is missing, and when a file is refused it prints this command with the id filled in. A reply fetched for another install's id, or for none, still verifies, but one made for another install reads as the free tier here. Carry `reply.json` to the offline box and pass it to `--file`. Where the bytes travelled does not matter: the signature is what is checked. ### Nothing is written unless it verifies Whatever arrives, from the network or from a file, is verified on your machine first, against the public key built into the program. It must verify, be in term, and say it is valid and entitled. Anything else is refused and nothing is written, so a bad activation never replaces a good file. Before anything is sent, `din activate` checks that what you gave it has the shape of a DIN licence key. A typo or the wrong paste is refused on your machine ("this is not a DIN licence key (check for a typo)"), and nothing is sent or written. ### What it writes - `/.din/entitlement.json` (by default `~/din/.din/entitlement.json`), which `din license` reads and which `din field start` and `din console` hand to the programs they start. - The same bytes to `~/.din/entitlement.json` (or `$DIN_HOME/entitlement.json`), the default a field or console started any other way, and the plugin, read. - If `DIN_ENTITLEMENT` (or `DASH_ENTITLEMENT`) names a file, that one file only. - After an online activation with a new key, the key is saved to `/.din/license.key`, so a later `din activate` on its own re-activates. Each file is written mode 600, through a temporary file and a rename, so a reader never sees half a file. ### Your install id The first time `din activate` checks in, it creates a random install id for this install: 32 hexadecimal characters (128 random bits) in `~/.din/install-id` (or `$DIN_HOME/install-id`), mode 600. It is made once and kept. Every check-in sends it with your key, and the licensing service signs it into the entitlement it answers with. The install id is a random number. It is not derived from your machine, your user name, your network or anything else about you, and it names no person and no machine. The licensing service keeps the ids your licence has checked in from, to see how many installs use the licence. There is no install limit, and a check-in from a new install is never refused because of it. The entitlement is tied to the install that fetched it. If you copy `entitlement.json` to another machine or user, it reads as the free tier there, and `din license` says "this licence was activated on another install; run din activate here". Run `din activate` on that install (with the key, or the saved `license.key`) and it gets its own. ### When it takes effect The field re-reads the entitlement on its rescan tick (every 5 seconds by default), so the paid features switch on within seconds without a restart. A `din console` that is already running picks it up too: reload the page. It then shows your plan, what it includes, your agents and when the plan renews. `din license` shows the tier, and who decided it, at any time, and `din status` shows your plan, when it renews and your agents. ### Renewing The signed entitlement on your install runs 14 days from the check-in that fetched it, whatever your plan's period, and each check-in fetches a fresh 14 days. It never runs past your key's own term. Each period's key runs a few days past its billing date, so a renewal that lands a day late does not drop you to free. Your subscription gets a new key each period. While it is live and paid, the licensing service answers the key you saved with the current period's entitlement and the current key; `din activate` checks that key on your machine and saves it in place of the old one, so the next renewal presents a key from this period. ```bash din activate --renew # check the saved key in again; prints nothing when it works ``` `--renew` uses the saved key only (give it no key and no `--file`). When it cannot renew it prints one line saying why, writes nothing, and the entitlement you have stays in place. To have it done for you, run `din autostart on` (per user, no admin). On a paid install the login entry also runs `din activate --renew`: with systemd, two minutes after login and then daily (a timer, `din-renew.timer`); with a plain XDG autostart entry, at each login. If autostart was already on before you activated, `din activate` adds the renewal to it and says so. `din autostart off` removes it all. Without autostart, a paid install checks in when you start it: `din field start` and `din console` run the same check-in as `--renew`, quietly, once its last check-in is a day old (and again when the entitlement has run out). Without autostart there is no timer: nothing checks in until you start DIN or run `din activate`. After 7 days without a successful check-in, `din license`, `din status`, `/din status` and the console's banner warn: "renews automatically with din autostart on; offline for N days". After 14 days the install reads as the free tier, saying "the licence has not been renewed for 14 days; run din activate --renew (or din autostart on)". Run `din activate --renew`, or `din activate` with the new key from your account page, or `--file` with a saved reply, offline. If the entitlement has expired, activation says so ("renew, then activate again"). A hand-edited entitlement, another key's signature, or a lapsed term is read as the free tier. Nothing in your records is deleted on a lapse. ### If a payment fails A failed renewal payment does not switch anything off straight away. Your paid features keep working for 7 days from the first failed payment while the card is retried, and `din license` warns with the date: ``` WARNING Payment failed. Paid features continue until ; update your card at ``` The payment-failed email names the same date. Update your card or pay the open invoice at any point in those 7 days and nothing changes. If it is still unpaid after the 7 days, the next `din activate --renew` installs the licensing service's signed answer that the plan has ended: the install moves to the free tier, the paid entitlement file is kept beside it as `entitlement.json.revoked-