Write the first half of the user documentation for imdUSD, a dollar-denominated CDP stablecoin in this repository: the overview, the borrower and redeemer guides, and the keeper guides. Deliver Markdown files only; a separate step renders them into the site. Do not modify any tracked file.

BEFORE WRITING, research how strong DeFi documentation is organised (the Diataxis split of tutorials, how-to guides, reference and explanation; and live examples such as Liquity, Aave and MakerDAO/Sky docs) and apply what you find. Summarise the practices you adopted, with links, in artifacts/docs/README.md.

PAGES IN THIS JOB AND WHAT EACH MUST COVER:

overview/what-is-imdusd: what it is, who it is for, what backs it, what is unproven, in under 500 words.

overview/how-it-holds-a-dollar: explanation of borrowing, redemption at the lesser of $1 and backing per imdUSD less the fee, liquidation, and the swarm-attested price (IMD/ETH from IdentityMD panels, times Chainlink ETH/USD), with the primary and spot divergence guard.

overview/glossary: every term the set uses (collateral ratio, mat, duty, line, chi, network health index, mark, grace, liquidation window, backing per imdUSD, reserve, stability fee, attestation, question hash, keeper).

guides/use-the-terminal: the terminal at /terminal/ (web/): monitor tabs, desk tabs, what each figure means, what disabled actions and their messages tell you.

guides/open-a-position, guides/manage-and-protect-a-position, guides/redeem: step-by-step tasks, each with prerequisites, the exact contract call underneath (lock, draw, wipe, free, cash), what can block it and how to recover. Protecting a position covers the liquidation price, how mat moves with network health, and that lock or wipe clears a mark.

keepers/how-liquidation-works, keepers/mark-and-liquidate, keepers/relay-oracle-updates, keepers/keeper-economics: bark and bite: marks, grace and the liquidation window; the bonus (CHOP_PERCENT) and how it splits into chip for the marker, cut for the protocol and the rest for the biter; clearing recovered marks with heel; relaying an attestation permissionlessly through SwarmRelay; why relayAndBite and relayAndBark bundle a relay with the action; the inventory a keeper needs.

CONVENTIONS (shared with a sibling job writing the other half; follow exactly). Every page is Markdown at the path given, opening with a front-matter block: title, section, order (integer), audience (borrowers | keepers | integrators | governance | everyone), and sources (repo paths with line numbers, or URLs, that support the page). Describe imdUSD plainly as what it is and how it functions, from this repository's current source. Do NOT mention testnets, Sepolia, test deployments, version history or anything as "currently" or "today": these pages ship with the mainnet launch and must not need revising after it. Every contract address is written exactly as "(waiting for mainnet launch)". The stablecoin is imdUSD. Quote every contract, function, event and error identifier exactly as in source. The vault's verbs and parameters (lock, free, draw, wipe, bark, bite, heel, cash, earn, drip; mat, duty, line, chi, CHOP_PERCENT, chip, cut, tail, gap, lull, skew, wage, earnLine, earnMat) are a deliberate homage to MakerDAO, partly borrowed and partly coined in its spirit, recorded with their origins in docs/NAMING.md: use them for identifiers, explain each in plain words on first use, and give the homage one sentence in the overview. Users never see them: the terminal labels every action in plain words, so overview and guide pages name actions exactly as its buttons do (Deposit, Withdraw, Borrow, Repay, Redeem, Mark, Liquidate, Clear mark, Mint from work) and give the contract function once alongside in code format, for example "Borrow (draw)". Reference, governance and economics pages lead with the identifiers. Every economic parameter VALUE, governed or fixed, is written exactly as "(under consideration)": the mat curve, duty, line, CHOP_PERCENT and its split between chip and cut, the redemption fee floor, cap and decay, gap, lull and tail, skew, feed maximum age, earnMat, earnLine and wage, and every bound on them. Explain what each is and how it works, never its number. Oracle updates purchased on chain through an Intake contract and funded from treasury assets are being built and are not in this source: describe only what the source implements, and where a page needs that mechanism write a visible line "TODO(oracle-funding): …" stating what belongs there, for us to fill. AUTHORITY: src/.sol is the truth. When docs/.md, the README or the whitepaper (https://infer.miyagod.eth.limo) disagree with the code, follow the code and note the disagreement in your README. Never invent an address, parameter value or function: read it from source or leave a visible TODO. Link between pages with relative paths, including into the sibling set listed below. Plain language, second person in guides, numbered steps for procedures, one idea per paragraph, units on every number, terms defined on first use. No marketing voice, no emoji.

FULL TABLE OF CONTENTS (both jobs): overview/what-is-imdusd, overview/how-it-holds-a-dollar, overview/glossary, guides/use-the-terminal, guides/open-a-position, guides/manage-and-protect-a-position, guides/redeem, keepers/how-liquidation-works, keepers/mark-and-liquidate, keepers/relay-oracle-updates, keepers/keeper-economics (job A); reference/contracts-and-addresses, reference/vault-functions, reference/events-and-errors, reference/oracle-and-question-binding, reference/reading-state, governance/parameters, governance/timelock-and-proposals, governance/network-health, economics/monetary-policy, economics/swarm-evidence, economics/risks-and-open-questions (job B).

DELIVERABLE: the eleven pages at artifacts/docs//.md, plus artifacts/docs/README.md stating sources used, practices adopted, every code-versus-doc disagreement found, and every TODO left.