Skip to main content
MKMIDIA KIASAT

Midia Kiasat

TECHNICAL PRACTICE

Engineering for observable consequences.

The recurring concern is not novelty in isolation. It is the path from intent to execution to evidence—especially when software acts across a real boundary.

  1. Law
  2. State
  3. Reconciliation
  4. Cognition
  5. Authority
  6. Execution
  7. Evidence
  8. Verification
  9. Recognition
  10. Recourse
SELECTED SYSTEMS

Architecture with public artifacts.

1 evidence refs

ADJUTORIX

Canonical system object for ADJUTORIX.

↗1 evidence refs

BOUNDARYCAM

The camera for machine action. Capture what crossed the boundary when agents, workflows, and autonomous systems act.

↗1 evidence refs

INVOCORDER

Machine-action evidence recorder runtime: hash-chained boundary records and replayable evidence bundles.

↗1 evidence refs

VERIFRAX

Core Verifrax verification protocol for authority-governed execution, evidence receipts, and deterministic trust.

↗

Operating principles.

01 / AUTHORITY

Permission precedes action.

Authorization and execution stay separate so a successful action is not mistaken for an authorized one.

02 / EVIDENCE

State leaves a receipt.

Inspectable records make it possible to reason about what crossed a boundary and what can be replayed.

03 / RECOVERY

Failure is part of the design.

Inventory, restoration, validation and handoff belong in the implementation sequence.

04 / TRUTH

Artifacts do not prove adoption.

Repositories and packages support bounded implementation claims, not customer, production or outcome claims.

PUBLIC ARTIFACTS

Source is evidence, not identity.

TypeScriptqzro/ADJUTORIXGitHub repository surface for ADJUTORIX.JavaScriptANTIMATTERIUM/ANTIMATTERIUMIndustrial antimatter economics, custody, storage, and starflight mission architecture.Pythonqxvi/BOUNDARYCAMThe camera for machine action. Capture what crossed the boundary when agents, workflows, and autonomous systems act.JavaScriptkaaffilm/CINEMATICUMCINEMATICUM produces admissible cinema.Swiftmidiakiasat/GX430TGitHub repository surface for GX430T.JavaScriptINVOCORDER/INVOCORDERMachine-action evidence recorder runtime: hash-chained boundary records and replayable evidence bundles.JavaScriptqxvo/MAILSIEVEBounded, resumable CLI for discovering publicly listed business email addresses from domain lists.Pythonkaaffilm/MK10-PROPre-delivery truth infrastructureRepositoryqvra/qvraFront door for qvra: route-first entry into the live field.HTMLVerifrax/SPEEDKITVerifrax root registry and governance surface: SPEEDKIT.JavaScriptTRUTHFRAMER/truthframer-platformThe object spine for TRUTHFRAMER: replayable visual truth frames for market reality.JavaScriptVerifrax/VERIFRAXCore Verifrax verification protocol for authority-governed execution, evidence receipts, and deterministic trust.PYPImk10-proPyPI distribution surface for MK10-PRO.

Cloud & production discipline.

Static-first delivery, explicit security headers, bounded machine-readable projection, recovery-aware architecture and verifiable build gates.

These are implementation disciplines represented by this public estate and its admitted case records. They are not a claim of universal security or external production adoption.

TECHNICAL WRITING

The argument behind the architecture.

EssayWhen AI Changes Code Without AuthorityEssayVerification Fails When Treated as WitnessingEssayExecution and Judgment Are Non-Substitutable
Engineering evidence boundary

Each selected system page links its admitted public repository and evidence references. Technical maturity remains distinct from external adoption and commercial outcome.