The reference standard, method, and plan release together
The reference standard. The Monument Method. The construction plan.
Intent preserved. Capabilities adapted. Evidence required.
influx.avi is the reference standard. The release build follows that plan from the first dependency to final proof and is evaluated against published acceptance gates. Builders will be invited to meet it, exceed it, or prove a different capability on hardware of their choosing. Its first planned package target is Apple Silicon macOS.
Reference standard · Challenge plannedMarkdown is the contract. Hashes bind it. Code serves it. Evidence proves only the named claim. Stop on drift. The human reviews, approves, and opens the next gate.
Read · Bind · Build · Prove · ReviewThe plan is the standalone source of product intent and construction requirements for Influx.AVI. It must allow a future engineer or AI to start with an empty repository, build the system in dependency order, and adapt every required capability to an unknown device or interface.
Full construction contract · In reviewWhy launch all three
The Method defines how construction-grade plans are made and executed. The influx.avi plan applies it to one system. The release build follows that plan from the first dependency to final proof. Releasing all three makes the intent, capability boundaries, build order, and proof standard inspectable on day one.
Independent builders can use the plan to create differently named implementations with their own agents and hardware. Those versions will not be official influx.avi releases, and design portability does not prove a working or supported port.