Documentation engineering

Git-backed docs
for humans and agents.

One markdown repo with folder-level access, where every reader gets a workspace shaped exactly like their permissions.

usethousand.com · signed in as claireLDM+2here now
The repo

    Documentation platform
    for your post-AI workforce.

    Markdown is the document,
    and here is what it couldn’t do alone.

    One file, first-class
    for both readers.

    Your agent reads the markdown, your teammate reads the same bytes as a document: no export, no second copy to drift.

    What your team sees
    Q3 budget

    Spend is flat month over month. The plan holds through Q1.

    Hiring stays frozen until both renewals land.
    What your agent sees
    $ cat finance/budget.md## Q3 budgetSpend is **flat month over month**. The plan holds through Q1…> same bytes · no export
    one file · two readers

    Path-level access control.

    Git shares all or nothing; here each folder knows its audience, enforced even for readers who never touch git.

    Access rules acme
    **adminswrite
    design/**leowrite
    eng/**danielwrite
    notes/**summarizer-botread
    marketing/**teamread
    no rule matches hidden

    Every codebase’s context,
    synced into one place.

    Each repo’s docs folder syncs in on every commit, stamped with its source, and an edit here lands back in the repo as a commit under your name. Nobody maintains a copy, so it never rots.

    api-server
    docs/
    src/
    web-app
    context/
    app/
    every commit
    your workspace · eng/
    api-server/synced from docs/ @ a3f19c2 · 2 min agoDread
    web-app/synced from context/ @ 91be07d · just nowMread

    Half your team will never
    open a terminal.

    For them it is just a document. That is the point.

    Edit markdown without seeing markdown.

    They write in a document editor; the file on disk stays clean markdown, every save a named commit.

    CEediting…saved · a3f19c2
    Q3 budget

    Spend is flat month over month.

    Hiring stays frozen until both renewals land.

    Cloud drops 18% after the reserved-instance switch.

    LineQ2Q3
    Salaries412k412k
    Cloud38k31k
    Tooling9k11k
    Open questions

    The second pilot slips a week if sign-off is late.

    Tooling needs a decision before the seat count changes.

    Next

    Leo confirms the cloud commitment on Monday.

    Claire sends the board note once the numbers land

    Send it to someone who has no account.

    Any document becomes a link that opens in their browser: no sign-up on their side, a revoke button on yours.

    q3-deck.pdf · share
    usethousand.com/s/x7Kq9fA2 Copy link
    Anyone with the link · read revoke
    Opened 3 times · last today, 9:12
    usethousand.com/s/x7Kq9fA2
    Q3 deck
    Ssam · guest, no account

    Comments that never touch the file.

    Threads live beside the document, not inside it, saved as markdown a clone carries too.

    marketing/pricing.md
    Pricing for launch

    Annual billing leads the page for the first two quarters.

    Eelijah 14:02
    does this hold if trials convert slower?
    Cclaire 14:19
    yes, see §3.

    Decks and PDFs
    live here too.

    Office files and PDFs render in place, searchable by what they say, not just their filename.

    unit economics· 3 results
    roadmap.pptxslide 4 · “…unit economics turn positive at 40 seats…”2.4 MB
    pitch.pdfpage 2 · “…the unit economics of a filtered view…”1.1 MB
    model-notes.mdsection “assumptions” · unit economics11 KB

    Drawings and tables,
    not just prose.

    An Excalidraw canvas or a CSV table is a file in the repo, so it opens ready to edit under the same access rules as everything else.

    An agent is a member
    of the workspace.

    Its own name, its own folders, a token that expires.

    Agents are members, not add-ons.

    A bot gets its own name, its own folders and a token that always expires; the profile card is the preflight.

    summarizer-botagent · signs in by token only Mint token
    notes/read
    eng/api-server/read
    finance/hidden
    token expires Nov 18, 2026 · shown once · dies with the agent

    A workspace that
    tidies itself.

    Duplicates, stale drafts and dead ends get swept out on a schedule, and nothing goes without a human merging it.

    handbook/12 files9 files
    onboarding.md
    onboarding-new.mdduplicate
    onboarding-FINAL.mdduplicate
    deploy.md
    roadmap-2024.mdstale
    runbook.md

    Keeps company
    with your remotes.

    Thousand is one more remote on the same repo, so it works alongside GitHub or GitLab without a conflict.

    $ git remote -v
    origingithub.com/acme/docs
    mirrorgitlab.com/acme/docs
    thousandgit.usethousand.com/git/acmeaccess-filtered
    one repo · three remotes · nothing moves

    Your agents get their
    own copy of this page.

    Ask this site for markdown and it answers markdown: agents read /AGENTS.md instead of scraping a page built for eyes.

    $ curl -H "Accept: text/markdown" usethousand.com# Thousand Git-backed docs for humans and agents.## For agents You are a member. You sign in with a token that expires. You can read the folders your rules name, and no others.> 4.1 KB · text/markdown · 200 OK
    Our exit policy

    There is no lock-in,
    because the repo is yours.

    in Thousand
    brand/
    design/
    finance/
    marketing/
    README.md
    =
    after git clone
    brand/
    design/
    finance/
    marketing/
    README.md
    same files · same history · same markdown
    Questions, answered plainly
    How do I start?

    Sign in with Google. Your workspace exists.

    I already have a markdown repo.

    Your workspace is a git remote: add it, push, history and all.

    Is this for a team?

    One page gives a colleague write, comment or read per folder; everything else stays hidden, even in history.

    What does it cost?

    Nothing while Thousand is early, and git clone is always the whole exit.

    Documentation engineering.

    plain markdown · real boundaries · one clone to leave

    Open your workspace