Praxis
Praxis is an interactive AI training tool, currently in development. It builds on a prior fire-support-reference project, a condensed, self-authored teaching reference for indirect-fire doctrine, written in 2022 by OUTURE's founder while serving in the Marine Corps.
The prior project rewrote a sprawling field-manual subject into a short document organized by decision sequence: which asset fits the target, who to call, how to describe it, what effect to ask for. The substance was unchanged; the structure was rebuilt around how a Marine actually thinks under pressure.
Praxis is the next surface for the same content. The decision sequence becomes a drill loop: the AI coach generates a scenario, walks the trainee through the call, validates the response, debriefs the choice, and resets a sharper version of the same problem. The reference is the floor; the coach is what closes the gap from "recognized when I read it" to "executed when it counted."
Field manuals cover everything and teach nothing. Indirect-fire doctrine sprawls across hundreds of pages (field manuals, MCI modules, JKO coursework) organized by topic rather than decision-making. A Marine will read 20 pages. They won't read 400. The gap between completing formal training and making a sharp call-for-fire under load is real; the existing reference is built for archive, not engagement.
Restructuring the content closed part of that gap. The next part is the surface: the same decision sequence as reps you run, not pages you read. Static reference beats field manual by an order of magnitude; reps with feedback are a different ceiling entirely.
The drill loop runs the standardized five-transmission call-for-fire: position report, warning order, fire mission, target description, message-to-observer readback. The coach generates the scenario (terrain, observer position, asset availability, target type), the trainee picks the asset, the direction method, and the desired effect (destruction, neutralization, suppression). The coach validates the format and the choice, debriefs what was off, and adjusts the next scenario.
Imagery grounding carries over from the prior project. Junior Marines absorb more from current, real terrain than from abstract training aids; scenarios are built from the same kind of commercial satellite imagery the static reference used, with restricted identifiers handled appropriately.
The architecture mirrors the rest of the OUTURE lab: generative where it pays, deterministic where it has to. The five-transmission schema is rule-validated against the actual format; a malformed call-for-fire is a failed transmission, not a stylistic note. The coach side is generative for scenario variety, narration, and debrief tone.
Why interactive over reference. Static reference improves over field manuals by an order of magnitude, but the ceiling is still the document. The trainee who recognizes the call-for-fire format on a page isn't the same trainee who runs it cleanly under pressure. Reps with feedback are the surface that closes that distance, and a document can't be that surface no matter how well it's written.
Why doctrine as a content problem, then as an interaction problem. The prior reference treated doctrine as a content-design problem. The substance was correct, the failure was structure. Praxis treats it as an interaction-design problem with the same posture: the decisions are unchanged; the surface meets the trainee where engagement actually happens.
Why this sits in the OUTURE lab. The same pattern shows up in civilian work all the time. Field manuals that teach nothing have a direct analog in internal wikis that onboard no one. Training that fades after course has an analog in onboarding that fades by week three. Tacit NCO knowledge maps cleanly to tribal knowledge about runbooks. The fire-support domain is honest about the stakes; the architecture generalizes to anywhere a static document is asked to do training-loop work.
Why peer-created. The prior reference wasn't authorized; nobody asked for it. Proximity to use drives authority. The people closest to a document's usage are best positioned to improve it. The same is true for Praxis. The agent isn't replacing the NCO; it's compressing what a good NCO does on a quiet afternoon (runs you through reps, watches your call, tells you what was off) into a surface a junior Marine can pick up between formal cycles.
Internal research, in development. The static fire-support-reference exists and stands on its own. Praxis is the next iteration of the same hypothesis: that doctrine treated as content, then as interaction, beats doctrine treated as archive.