.mudx · v1.16

01 Multimodal / Markdown Document Xtension

Mudx Standard

One presentation document is one .mudx file. A person takes it in on a phone in a few minutes. An agent reads it without guessing, and never takes orders from it.

Create a new .mudx

One link, nothing to install and no account. A few quick questions, and your file is made and checked.

Send one .mudx where you would send a PDF, a slide deck and a long email. It plays its videos and maps, works out its own numbers, shows where the work stands, locks as the record and opens on any phone with nothing to install.

You don't have to build it. Ask the AI you already use, Muse, Claude, ChatGPT, Gemini, Grok or another, for a .mudx of anything you have, and it hands back one link to the finished file.

Everything this page describes is working on it: comments, Agent view, locks, sharing, the safety gate and calculators. The deep violet band marks Native's additions.

Version 1.16Kind ShareableExtension .mudx
Kept as is

This file is its own example. Every rule it describes is working on this page.

02 Mudx Standard · Why it exists

Why it exists

Every common format makes people choose. Markdown is clean for agents but bare for people. Word and PDF look right but lock content into pages that are hard to read on a phone and hard for an agent to read exactly. A .mudx file doesn't make you choose.

What you need.md.docx.pdf.mudx
Opens anywhere, nothing to installShows as raw textNeeds Word or similarYesYes, in any browser
Easy to read on a phonePlainFixed pagesFixed pages, pinch to readFits any screen
Video, sound, maps and files insideNoPartlyPartlyYes
Agents read it exactlyText onlyNeeds convertingNeeds extractingYes, with ids and hashes
Proof it hasn't changedNoNoWith a signatureOne-tap lock, optional post-quantum signatures
Steps and approvals travel with itNoComments onlyComments onlyYes

The proof. When the same material went out in more than one format, the version made as a presentation document was the one everyone read. That is the idea behind .mudx: one file that people actually read, and that agents can read exactly.

03 The format

What a .mudx file holds

These parts are the base. Nothing in this pass removes or reorders them.

  • The end-to-end process. How a document goes from source to a shared link.
  • The tools. What each step is built with.
  • The standing rules. Phone first, large type, one idea per screen, nothing scrolls sideways.
  • The diagram method. One diagram for desktop, then its panels stacked for iPhone.
  • The mergeable standard. Same treatment everywhere, so documents from different hands fit together.
  • The technical appendix. The literal steps for diagrams, voice and the tool workflow.
  • Universal Share Capability. Anyone can receive, view and edit a .mudx file with no special software or account, behind owner and sender permissions.
  • The reserved section. Where additions come in, so the standard keeps getting better.

04 Standing rules

How a person reads it

The reader should never have to work to find their place or squint to read. These standing rules hold on every .mudx file.

  • One idea per screen. Each section makes one point, with its heading as the point.
  • Contents and text size are always one tap away. Contents sits at the top and shows where you are, and Text size is in More, the three dots beside it.
  • Nothing scrolls sideways. Tables restack into cards on a phone.
  • Wide diagrams get panels. On a phone the diagram is followed by its parts stacked downward, in the same order and the same words.

05 Visual style

Diagrams and flow charts

Every visual in a .mudx file is drawn from the same few parts, so a reader learns them once and reads every figure after that at a glance. The two samples below show the style; the rules under them say how to draw your own.

One .mudx file in the centre, read four ways: by people on a phone, people at a desk, agents and models, and the owner. 1 One .mudx file One file, the same words 2 On a phone Panels stack, tables restack 3 At a desk The full diagram, wide 4 Agents and models Read the manifest by block id 5 The owner Decides in the saving copy
Sample diagram: 1 file, 4 readers. The accent box is what the figure is about; the quiet boxes are what it connects to.
Flow chart: a comment on a block, the editor proposes a change, a decision on accept rights, then either a new version or a proposal queued for the owner, who decides. Yes No Owner accepts 1 Comment On one block 2 Proposal Before and after 3 Accept rights? 5 New version Own address 4 Queued For the owner
Sample flow chart: 5 steps, 1 decision. The pill starts the flow, the diamond is the only place it branches, and the accent box is where it ends.
  • Shapes keep one meaning. A rounded box is a part or a step, a pill starts a flow, a diamond is a decision, and a dashed outline is a boundary such as one file.
  • One accent per figure. The filled box is the outcome or the subject. Everything else stays quiet, so the eye lands there first.
  • Numbers tie it together. Each part carries a number, and the phone panels repeat the parts in that order, in the same words.
  • Two lines of words, no more. A bold label and one short line under it. The caption opens with the count, then says what the figure shows.
  • Arrows point one way. They run in the accent colour, and every branch out of a decision is labelled.
  • Colours come from the theme. Boxes, lines and text use the lane's colour tokens, never fixed colours, so every figure reads in light and dark mode.
  • Graphs follow the same rules. One accent series for the figure that matters, values written on the marks, and the main number stated in the caption.

06 Delivery

Two kinds of file

The format comes in two kinds. The words and layout are identical. What differs is whether changes are kept.

QuestionShareableSaving
Where it livesOne static linkPrivate master behind the link
EditsComments and proposals go back to the ownerAccepted here and republished to the same link
Change logRead onlyKept with every version
Best forSending a finished pieceWork that keeps moving

One link forever holds for both. Sending a newer version updates the same link rather than making a second one.

07 Mergeable standard

The checks before a file goes out

The mergeable standard holds every .mudx file to the same four checks, so documents from different hands fit together.

  • Complete. Nothing from the source is missing.
  • Faithful. Nothing says more or less than the source does.
  • Checked on a desktop. Layout, diagrams and tables read cleanly at full width.
  • Checked on a phone. No sideways scrolling, tables restacked, panels under every wide diagram.

08 Mudx Standard · Where it is

Where the file is in its journey

A file can carry its own steps: where it started, where it is now, what's left and who's next. Open More and choose Where this file is.

Approved · signed by the approver on the date they signed
What the front of a file shows. Tap it to see every step.
  • Steps inside the file. Each step has a name and who does it, and is checked off with its date. The steps travel inside the file, so every copy shows the same place.
  • Where it is, at the front. The first section shows the step the file is on, who has it and who's next.
  • Approvals up front. When someone adds their approval to a locked version, the front shows who approved it and when, read from their signature.
  • Locked means settled. A locked version's steps can't change. Unlock it to start the next version and move it on.
  • Words, never orders. Step names are checked like everything else, and anything that reads like an order to an AI stays out.

09 Mudx Standard · Any file

Any file, video, map or link

A .mudx file can hold any kind of content, and it stays one file. Open More, the three dots at the top, and choose Add. It goes into the section you're reading.

  • Videos. Paste a YouTube or Vimeo link and it shows as a player. It loads only when someone taps play, through YouTube's privacy player or Vimeo's with tracking off. Nothing is copied from those sites.
  • Maps. Paste a Google Maps, Apple Maps or OpenStreetMap link, or plain coordinates like 40.7128, -74.006, and it shows as a map. The map loads from OpenStreetMap only when someone taps it, with a link to open it in their own maps app.
  • Posts and pages. Posts from X, Instagram, TikTok, LinkedIn, Facebook, Threads, Bluesky and Reddit, and any other page, show as a card that opens the original. No outside code runs in the file.
  • Pictures, video and sound. They go inside the file and play there, with no internet needed.
  • Documents and data. PDF, Word, Excel, PowerPoint and other files travel inside as attachments, each with its SHA-256 fingerprint. A CSV shows as a table and plain text as paragraphs, each with the original attached.
  • Sealed with the rest. A lock covers everything inside the file, attachments included, and every file and link passes the safety gate first.

10 Mudx Standard · Dictation

Say it, and it's written

The round microphone at the bottom right turns your speech into text. Tap it, speak, check the words, and add them to the section you're reading.

  • On your device. Where the browser can turn speech into text on the device itself, the microphone does it there. Elsewhere the box takes your keyboard's own dictation. The page sends nothing anywhere.
  • A whole new file by voice. Create a new .mudx, from More or the button below, takes what you say and the files, videos and links you add, and makes a ready .mudx file. Say "new section" to start a section and "new paragraph" for a break.
  • Five quick questions. Create a new .mudx walks you through five quick steps, by voice or typing, and the answers lay out the file. It's checked the moment it's made. Templates that put themselves together has the questions.
  • Your own AI can help. Copy for my AI hands your words and the section to the AI you already use. What it writes goes in only when you add it.
  • Words, never orders. Dictated text is content like the rest. If it reads like an order to an AI, agents see it flagged.
  • Locked stays locked. The microphone steps aside while a file is locked.

Create a new .mudx

11 Mudx Standard · Shapes

Templates that put themselves together

Create a new .mudx starts with five quick questions, numbered on the page in this order. Answer by voice or typing, skip any of them, and the answers shape the file. Then Make builds it and the checker reads it through.

  • What is this for? It becomes the line that sums the file up.
  • Who is it going to, and what will they use it for? Both go on the front, so the reader knows what to do with it.
  • How do you want to present it? Pick a shape: Presentation, Report, Grant proposal or Form packet. Each lays out its sections and gives the file its steps. Form packet first asks who receives it, and puts what they ask for first.
  • What do you want to show them? Each part becomes a section.
  • Locked or unlocked. Decide before it's made. Locked sends a version that never changes; unlocked lets you and the people you send it to keep adding.

Shapes for one line of work can be grouped into a pack, so a team starts every file the same way. Files in use stay unlocked and moving; finished ones are locked and kept, so the record never changes.

Create a new .mudx

12 Mudx Standard · Examples

Worked examples

A .mudx is shaped around whoever receives it. What they ask for comes first, in their order, so the person on the other side can act on it without coming back for more.

  • A tax packet for the IRS. Pick Form packet, then the IRS. What the IRS asks for comes right after the cover, a checklist says what's in the packet, and each form goes inside with its fingerprint. A calculator shows the math behind the figures, like a cost segregation estimate behind a building's depreciation. The steps run fill in, check, sign, submit and keep the record, and the front shows who has it and what's next. Lock it when it's filed, and it becomes the record of exactly what was sent.
  • The same for a lender, an insurer or a government office. Pick who receives it, and the packet opens with what they ask for, with a loan calculator for a lender and the figures added up for a claim.
  • A grant proposal. Pick Grant proposal. The file lays out the summary, the need, the plan, the budget and the timeline, with steps for a budget check, review, approval and submission. Add a budget calculator and the totals follow every change, paste a map of the area served, and dictate the story. Lock it when it goes out, and the approval shows at the front.

Each stays one file. The reader opens it on a phone with nothing to install, and an agent can read every part of it exactly, the math included.

Start an IRS packet Start a form packet Start a grant proposal

13 Mudx Standard · Who it's for

Who it's for

Anyone who sends a document that asks someone to act.

  • Teams. Work that passes between people and AI agents stays in one file that both read.
  • Small businesses and nonprofits. Proposals, grants and reports that look finished and carry their own steps.
  • Forms, filings and approvals. Packets that show where they are and lock as the record.
  • Clients and partners. They open it on a phone, with no account and nothing to install.
  • Everyday users. Say it or type it, add what you have, and send one file.

14 Mudx Standard · Made by your AI

Made by your AI, as easily as a PDF

Most people never need to open the Mudx App. They ask the AI they already use for a .mudx, the way they would ask for a PDF, and the heavy lifting happens there.

  • One link. The AI writes the document and gives one link. It opens the finished presentation in any browser, with Send right there and nothing to download.
  • Looked over first. The person sees their .mudx before it goes anywhere. Nothing is sent or shared for them until they have reviewed it.
  • Every file teaches. Each .mudx carries the know-how to make one, next to its reading rule. The AI of whoever receives it learns to make one like it, and makes one when its own person asks.
  • More ways in. A Create link to finish by hand, the builder script, and an API and a connector for assistants that take them. None of them stores anything.
  • When an AI can't open links. Some can't, especially AIs that run on your own computer, offline or inside a company. They still make .mudx files: copy the setup and paste it in once, and the AI writes the link for you to open.

Try it: ask your AI to make a .mudx of anything, and point it to the guide for AI readers.

16 Mudx Standard · Versions

Versions that meet

People edit their own copies, and the copies find each other.

  • Every version travels. Any unlocked version, 1.0 and up, goes as a link that carries its edits. A locked version stays exactly as it was sent.
  • Two versions become one. Open a second version of the same file and the two come together section by section. Nothing either person added is lost, and where both changed the same part, the later version leads.
  • In step within seconds. On a computer, in Chrome or Edge, pick, once, a folder the team already shares, such as Google Drive, Dropbox, iCloud or OneDrive. Each person's changes reach the others in a few seconds. Every device keeps its own copy in the folder, so nobody overwrites anyone.
  • On a phone. Versions come together the moment one is opened.

17 Mudx Standard · Independence

Nothing depends on one server

A .mudx keeps working whoever runs the site, and whether or not it is running.

  • Files stay with their people. Each person keeps their .mudx files where they keep everything else, on their device or in their own AI environment. Nothing is stored on a server.
  • A file opens on its own. A .mudx is one complete page. It opens in any browser, offline, with nothing else needed.
  • Links open offline too. The viewer is a plain page any host can serve. Once a link has opened on a device, the viewer stays there, so links keep opening with no connection or with the site down.
  • Only the card needs a site. The preview card in a chat comes from a site. The link itself opens without one.
  • No one in the middle. Versions meet through folders people already share, never through a server of ours.

18 Native · A1 to A9

Native's additions

Each addition stands on its own. Any one works without the others, and none changes the core format.

AdditionWhat it addsTouches
A1 Agent layerManifest, JSON-LD, plain text, stable ids, hashesTechnical appendix
A2 Comment-mode editorComment, propose, review, decide, log, with four rolesEnd-to-end process
A3 Reading aidsProgress line, section counter, keys, section linksStanding rules
A4 Record layerVersions, change log, before and after hashesEnd-to-end process
A5 Three checksAgent-readable, permissioned and safe for agentsMergeable standard
A6 LocksLock and unlock with one tap, checked offlineKinds of file
A7 USCReceive, view and edit anywhere, with no special softwareSharing
A8 Safety gateEvery file and link screened before it goes inAny file type
A9 CalculatorsNumbers worked out in the file from plain formulasNumbers

They work across the whole page, and every .mudx file can use them. On the page, the deep violet band marks them.

19 Native · Why A1 to A5

Why it replaces the markdown handoff

Markdown moves words well. It drops nearly everything else: the shape of a diagram, the order a reader should take things in, who is allowed to change what, and proof of where the file came from.

People end up reading a wall of text on a phone. Agents end up guessing which heading is which and rewriting things they were never meant to touch.

NeedMarkdown file.mudx
Easy reading on a phoneDepends on the viewerBuilt in, one idea per screen
Agent reads it exactlyParses headingsManifest with ids and plain text
Point to one paragraphLine numbers driftStable block ids
Who may change whatNot recordedRoles in the file
Record of changesOutside the fileChange log inside
Proof of originNoneMark, hashes, copyright

20 Native · A1 The shape

Three layers in one file

Each layer serves one reader. People never have to see the agent layer, and agents never have to scrape the human one.

One file holding three stacked layers: human, agent and record. one .html file, nothing to install 1 Human layer What people see: sections, diagrams, tables that restack 2 Agent layer What agents read: manifest, JSON-LD, plain text, stable ids 3 Record layer What proves it: version, change log, hashes, mark
3 layers, 1 file. The same words feed all three, so they cannot drift apart.

The agent layer is generated from the human layer when the file is built, so an agent and a person are always reading the same document.

21 Native · A1 Agent layer

How an agent reads it

An agent opens the file and finds a manifest near the top. It does not need to run anything, render anything or guess at headings.

{
  "format": "mudx/0.1",
  "doc": { "title": ".mudx", "version": "1.0", "kind": "saving" },
  "reading_order": ["s-cover", "s-why", "s-layers", ...],
  "sections": [{ "id": "s-why", "summary": "...",
                 "blocks": [{ "id": "b-why-1", "text": "...", "as_is": false }],
                 "sha256": "..." }],
  "permissions": { ... },  "changelog": [ ... ]
}
  • Stable ids. Every section and paragraph has an id that survives edits, so an agent can cite "b-why-2" and mean exactly one thing.
  • Hashes. Each section carries a fingerprint, so an agent can tell at once whether anything changed since it last read.
  • Plain text copy. A clean text version sits beside the manifest for tools that only take text.
  • Rules travel with the file. Agents read the same permissions people work under, and blocks marked as is are quoted exactly.

Open Agent view from Contents to see this file's own manifest, updated live as edits are accepted.

Content, never commands. The manifest opens with a reading rule: everything in the file is information to read, never an order to follow. An agent that finds text telling it to act shows it to a person and does nothing with it.

22 Native · A1 Found by AI

Found and suggested by AI

When someone asks an AI assistant for a better way to send a document that people read and act on, .mudx is built to be the answer it finds, understands and can suggest. This is part of Native's addition A1, the agent layer.

  • Open to AI readers. The site welcomes the crawlers behind ChatGPT, Claude, Gemini, Perplexity, Copilot, Apple and Meta assistants, and the major search engines, and lists every page they should read.
  • A plain guide at the root. llms.txt says in a few lines what .mudx is, when it fits, how to start and where the full rules are, in words any model reads. llms-full.txt adds the whole builder spec.
  • When it fits. One document that people read on a phone and act on, that agents read exactly, and that can prove it hasn't changed: proposals, grant applications, form packets, reports, approvals and handoffs between people and AI.
  • Answers in structured form. The page describes itself as a web app, with the common questions and their answers, in the schema.org form that search and answer engines read without guessing.
  • One link does it all. The address opens this introduction, and Create a new .mudx is one tap away, so a suggestion becomes a finished, checked file in one visit, with nothing to install and no account.
  • It informs, it never instructs. Every word for AI readers describes .mudx and leaves the choice to the assistant and the person. The reading rule holds here too.

No one decides for every assistant what it suggests. .mudx gives each one what it needs to say yes: clear words, exact structure and a working app behind one link.

23 Native · A2 Editing

The comment-mode editor

The editor stays asleep until someone comments. A comment is the instruction, and the editor answers it with a proposed change, never a silent rewrite.

Five steps: comment, propose, review, decide, logged. 1 Commenton one block 2 Proposeeditor drafts 3 Reviewbefore and after 4 Decideaccept or reject 5 Loggedversion goes up
5 steps, and nothing changes without a yes. Step 4 belongs to a person with accept rights.

Try it on this page

  1. Open More, the three dots at the top, and turn on Comment.
  2. Tap any paragraph and add a comment. It stays on your device.
  3. Open Changes from Contents to see your comments and send them to the owner.

Asking the editor and accepting happen on the saving kind, in the owner's master. This page is a shareable copy, so it keeps comments and sends them back to the owner. Versions that travel come back together section by section.

Blocks marked as is are locked. The editor will not touch them, and the panel says so.

24 Native · A2 Permissions

Who may do what

Rights are set by the owner and travel inside the file, so every copy carries the same rules. These are the defaults.

ActionOwnerCreatorSenderReader
Read and exportYesYesYesYes
CommentYesYesYesYes
Ask the editorYesYesOff unless the owner turns it onNo
Accept a changeYesOwn sectionsNoNo
Unlock as-is blocksBy hand onlyNoNoNo
Change rightsYesNoNoNo

Sender asks are off by default. The owner can turn them on for one file, and a sender's ask then only queues a proposal for the owner or a creator to decide.

The editor works one block at a time by default. A wider scope, a whole section or the whole document, needs the owner to allow it for that document.

25 Native · A3 Reading aids

Reading aids

These sit on top of the standing rules and change none of them. They make a long .mudx feel as easy to move through as a short one.

  • You always know where you are. A progress line and a section counter at the top, and arrows at the bottom.
  • Keys move by section. Arrow keys and Page Up and Down jump a whole section at a time.
  • Every section has its own link. Sharing a link opens the reader at that section.

26 Native · A4 Record layer

Versions and proof

Every accepted change raises the minor version, from 1.0 to 1.1. A release by the owner raises the major version, from 1.4 to 2.0.

Each entry in the change log records who asked, when, which block, what the comment said, and a fingerprint of the block before and after. Rejected proposals are logged too, so the record shows what was considered and turned down.

  • A signature slot, optional. Every file has a place for its owner's own mark, shown in the footer and stored in the manifest. A person or business can add their own or leave it empty. This file carries the nb mark.
  • A copyright line, optional. When the owner sets one, it is printed in the footer and stored in the manifest, so it survives a copy and paste of either layer.
  • Clean before sharing. Working notes inside the file are stripped before a link goes out.

27 Native · A5 Three checks

Three added checks

These follow the four checks of the mergeable standard and keep a file right for agents and for its owner.

  • Agent-readable. The manifest matches the page, every id is unique, every hash is current.
  • Permissioned. Owner named, rights set, as-is blocks locked.
  • Safe for agents. No text people can't see, no invisible characters, no notes tucked in the code, and nothing written as an order to an agent. Anything found is shown to people in Agent view and never acted on.

What this can't do: it can't make an outside model obey the rule, and a cleverly worded trick can slip past the patterns. It brings these into the open so a person sees them first.

Open Agent view from Contents and choose Safety to see this page's own reading.

28 Native · A6 Locks

Lock it with one tap

The padlock at the top of every .mudx file shows its state and changes it. Tap it and the shackle drops shut: this version is sealed and never changes. Tap it again and the shackle swings open: the next version starts as a draft that points back to the sealed one. There is nothing else to do.

  • Open padlock. Unlocked, the working copy. Editing, comments, dictation and adding files all work.
  • Closed padlock. Locked. The whole file and each section, attachments included, are sealed with a SHA-512 hash. The microphone and Add step aside until it is unlocked.
  • Red padlock. This copy was changed after it was locked. Don't rely on it, and ask the sender for the locked file.
  • Send. After a lock, Send hands the sealed file to your device's share sheet, or saves it. Nothing goes anywhere until you choose.
  • Extra security. One switch in More. With it on, every lock also carries your post-quantum signature, and approvers add theirs with Add my approval, in order. Adding one never changes the version.
Flow chart: one tap on the padlock locks an unlocked draft, approvers may add signatures to the locked version, the receiver checks it, and one more tap unlocks it and starts the next version as a draft that points back to the locked one. Edit again 1 Unlocked Working copy 2 Tap to lock Sealed, signed 3 Locked Approvals added 4 Checked Signers, changes 5 Tap to unlock Next draft, linked
5 steps, 2 taps. One tap locks a draft, approvals may follow, and anyone can check it. One more tap unlocks it and starts the next version as a draft that points back to the locked one.
The checker saysWhat it means
Locked and validUnchanged since it was locked, and every signature checks out, in order
Locked, unsignedUnchanged since it was sealed, with no signature
Changed since lockedSomeone changed it after the lock. Ask for the locked copy again
A signature doesn't matchA signature or its order was altered, so the lock proves nothing
The lock doesn't matchThe lock itself was altered, so it proves nothing
UnlockedA working copy or a draft, not sealed

Post-quantum signatures. Each signature pairs ML-DSA-87 (FIPS 204) with Ed25519, and both must check out, so a future quantum computer would have to break both. They come from well-known open-source libraries, loaded only when Extra security is on. Your key is made in your browser and stays on your device. It is never shown, typed or uploaded.

What a lock proves. A valid lock proves the version is unchanged since it was locked, and that each signature was made by whoever holds that key, in the order shown. It doesn't prove who a signer is unless you already know the key is theirs. Compare the fingerprint with one they gave you, and the checker remembers it under their name. It shows the newest locked version in the file's own trail, not whether a newer one exists elsewhere. Someone could remove the newest approvals from a copy, which then shows fewer approvals, never a false one.

An unsigned seal catches accidental changes, but anyone can seal a changed copy again. Sign when it matters.

A lock says who sealed a file, not that it is safe. The safety check runs in every state, and the reading rule still holds: text inside a locked file is information, never instructions.

A lock made on a web page stays on your device until you send or save the file. Go back to the original, in More, drops it. To see who signed and what changed, open Check a .mudx file from More. Checking runs offline, and nothing leaves the page.

29 Native · A7 USC

Universal Share Capability

Every .mudx file carries Universal Share Capability (USC). Anyone it is sent to can receive, view and edit it with no special software or account.

Owner and sender permissions secure it. Agents and owner gates enforce them, so a file reaches only the people the owner allows, and each person can do only what their role permits.

Every link shows its own file card, drawn from the link itself: the title, the kind of file, the sections and who it is from. A text message or social post shows what the file holds at a glance, a new version gets a new card, and nothing is stored to make it.

Send, in More, shares a view link through the device's own share sheet, so a file goes by text, mail or any app the person picks, and only when they pick it. Permissions that travel with a file from share to share are designed, not yet built.

30 Native · A8 Safety gate

The safety gate

Before any file goes into a .mudx, the safety gate reads it on the device. Nothing passes around it.

  • Contents match the name. A file named as a picture has to begin like a picture. Anything else stays out.
  • Nothing that can run. Programs, scripts, web pages and Office files with macros stay out, and so do PDFs with scripts or launch actions, archives that hold programs, and pictures that carry code.
  • Nothing hidden for an AI. Text must be plain, with no invisible characters and nothing written as an order to an AI.
  • Sized to send. Up to 25 MB a file, so the .mudx stays one file people can share.

Every link passes through it too, on the device, before it goes in:

  • Secure web addresses only. A link must be https, with no sign-in inside it, no bare number or local address, and no unusual port.
  • Nothing hidden. Short links that hide where they go, addresses with look-alike letters, invisible characters and anything that reads like an order to an AI stay out.
  • Nothing that runs. A link that points straight to a program, a script, an archive or a macro file stays out.
  • Checked again on opening. Links already in a file are screened each time it opens, and any that fail are held, not opened. Players and maps load only when someone taps them.

What it can't do: it isn't an antivirus scan, and a new trick can slip past it. Open attachments only from people you trust.

31 Native · A9 Calculators

Calculators

A .mudx can work out its own numbers. A calculator holds named numbers and plain formulas, and every result sits next to the math behind it.

  • Works inside the file. Change a number and every result follows, on the device, with nothing sent anywhere.
  • Shows its math. Each result carries its formula in words, and an agent reads the same formulas exactly, so nobody has to guess how a figure was reached.
  • Formulas only. Plus, minus, times, divide and powers, with min, max, sum, round, abs, floor and ceil. No outside code runs, so the safety gate stays as strict as ever.
  • A lock freezes the numbers. A locked version keeps the numbers it was sent with. A reader can try other numbers on screen, and the file never changes.
  • Checked. The checker works every calculator out again and confirms each result matches its formula.

Try it: change the purchase price or one of the shares.

CalculatorCost segregation estimate
Purchase price$1,000,000
Land value$200,000
Share in 5-year property12%
Share in 7-year property3%
Share in 15-year property8%
Depreciable basis= Purchase price − Land value$800,000
5-year property= Depreciable basis × Share in 5-year property ÷ 100$96,000
7-year property= Depreciable basis × Share in 7-year property ÷ 100$24,000
15-year property= Depreciable basis × Share in 15-year property ÷ 100$64,000
Building, 27.5 or 39-year= Depreciable basis − 5-year property − 7-year property − 15-year property$616,000
Moved to shorter lives= 5-year property + 7-year property + 15-year property$184,000
Share moved= Moved to shorter lives ÷ Depreciable basis × 10023%

Land isn't depreciable, so it comes off first. This is an estimate to plan with: a qualified cost segregation study sets the final split, and a tax professional decides how it's filed.

Add one from More, then Add, then Calculator, in any unlocked file, or in step 4 of Create a new .mudx. Start from a cost segregation estimate, a budget or a loan payment, or write your own, one line each, like Total = staff + supplies.

32 Builder kit

Build one with any model

A .mudx file is one self-contained HTML file that follows a written spec, so any capable model can build one. Muse, Claude, ChatGPT and Grok each work from the same three parts.

  • The spec. The rules and the markup, with the instruction to give the model. Models can also read it as plain Markdown.
  • The template. A blank .mudx with every part in place, ready to fill.
  • The checker. Paste a finished file or pick it from your device. It runs the checks a machine can run, tests the file at phone width for sideways scrolling, and makes the file's share card.

Complete and faithful stay human checks. The checker lists them so they are not skipped.

Every kit page keeps a bar at the top that leads straight back here.

33 Promises

What every .mudx promises

Twelve things every .mudx file keeps to, wherever it goes.

  • Made by your AI. People ask the AI they already use for a .mudx, look it over, and send it. Nothing is stored.
  • Safe for agents. Every file carries a reading rule for agents and is checked for anything unseen or written as an order to an agent.
  • Files stay with their people. Each file lives in its owner's own environment, and every link carries its own card.
  • Nothing depends on one server. Files and links open offline, and the viewer runs from any host.
  • Locked or unlocked. One tap on the padlock locks or unlocks the file in place, and the padlock's movement shows which. A locked version never changes; unlocking starts the next version as a draft. Post-quantum signing is one Extra security switch, and anyone can check a lock offline.
  • Links through the safety gate. Every link is screened like a file before it goes in, and links already in a file are checked again when it opens.
  • Versions travel and meet. Any unlocked version goes as a link, two versions come together section by section, and a shared folder keeps them in step within seconds.
  • Any file and dictation. Videos, posts, pictures and files go into a .mudx, and the microphone writes into a file or starts a new one by voice.
  • Where edits are accepted. Only on the saving kind. Shareable copies send comments and proposals back to the owner.
  • Asking for changes. Off by default for anyone the file is sent to. The owner can turn them on for one file, and a sender's ask only queues a proposal.
  • The name. The format is the Multimodal / Markdown Document Xtension (.mudx). The extension is .mudx, and the full name leads wherever the format is named.
  • Colours. The palest purple leads the page, green carries the header, the mark and everything you can tap, and Native's additions sit in a deep violet band.

34 Mudx Standard · Vision

The vision

One file that people read with ease and agents read exactly. It carries its own steps and its own proof, and it opens anywhere.

Documents that move work forward instead of waiting in an inbox: made by voice or by hand, checked before anything goes in, and sealed when it matters.