CODE AS STRUCTURAL ENGINEERING.
DOCUMENTATION AS BLUEPRINT.
// mujun.dev/manifest struct Workspace { name: "mujun.dev", material: "reinforced concrete", load: 4.2_tons/m2, modules: [ "structures", "protocols", "telemetry", "archives", ], exposed: true, }
This is a workshop, not a showroom.
mujun.dev is a documentation field. Code is poured like concrete: measured, reinforced, and left visible. Each module declares its purpose at the lintel, each function bears a serial. The structure is the ornament.
The split-screen runs throughout — left zone holds the engineering, right zone holds the explanation. Two sides of one slab.
The catalog of standing modules. Each one fabricated on-site, load-tested, and stamped with a revision mark.
Load-bearing primitives. Beams, columns, slabs. Nothing decorative.
Wire formats and handshakes. Specified to the last byte.
Strain gauges on every member. Continuous reading.
Cold storage of revisions. Cast and labelled.
A five-floor system. Foundation to roof, every floor visible.
Live readings from the structure. Strain, deflection, drift — measured continuously, never averaged out.
[04:21:08] sensor.S03 strain=0.62 nominal [04:21:09] sensor.U01 uptime=99.2 nominal [04:21:10] sensor.D02 drift=0.14 nominal [04:21:11] sensor.R04 rebar=0.83 nominal [04:21:12] system OK — slab cured 28d [04:21:13] cron archives.flush() [04:21:14] proto handshake v3 ack [04:21:15] system awaiting load…