Speculative DVM ontology sandbox. Not a decipherment. Did not influence model training. Mahadevan numbers are opcode indices, not recovered readings.
Zone 4 · InduScript v0.01
Operational DVM lab
Language spec · v0.01
A constructed stack language
InduScript is object-oriented in the small (Packet, Permit, Cargo, Key live on the stack) and RISC in the large (one pictogram-index, one command). Turing-complete only inside a bounded civic loop. Zone 4 only.
Opcode
M_001 … M_417. Each index is a constructed command, not a recovered Indus reading.
Modifier
M_150[M_402] applies a diacritic (here: three-node multisig) to a base call.
Ligature
<M_260 : M_350> is an atomic lock — all inner ops commit, or the stack rolls back.
Boustrophedon
Lines split by |. Line 0 LTR, line 1 RTL, line 2 LTR. Odd 0-based lines reverse token order.
Halt
M_005 stops the machine. Civic loops are bounded (256 cycles).
Object types on the stack
- packet — river or messenger datagram; status unverified | verified | lost
- cargo — commodity with quantity; yield division mutates qty
- weight — binary weight system (1, 2, 4, … 8000)
- worker / identity / permit / key — civic objects
- op — default wrapper so every one of the 417 codes is executable
What this language refuses
- It does not claim that M_342 meant a wall, a tax, or a jar in Harappa.
- It cannot write back into the canonical ledger (Z₁) or train the structural model (Z₃).
- A successful contract is a sandbox trace, not an inscription reading.
Prefer dotted notation? The ISX Codex compiles ISX::298.177 into this language and runs the same VM.