CPUX Authoring Tool

The CPUX Authoring Tool helps an architect move from Situational Reality to an executable Intention Space design seed.

The workflow starts with a scenario expressed in ordinary language. From there, phrases are discovered, reviewed, mapped into Intention Space roles, grouped into CPUX interaction containers, checked against architectural invariants, and exported as JSON or Markdown.

This version is intentionally lightweight. It is designed to run as a static component inside this site, while optionally connecting to the WordPress-hosted ISC Phrase API introduced in the Phrase Collector console.

Five-stage Workflow

CPUX Author Console

<label>Project name</label>
<input id="projectName" value="Cloud Architecture CPUX Draft" />

<label>Scenario</label>
<textarea id="scenarioText">A learner wants to deploy a small containerized web app for users in India and Australia. The app should be low cost when idle, survive a zone failure if possible, and avoid unexpected network or load balancer cost.</textarea>

<div class="cpux-row">
  <button id="loadCloudExample" type="button">Load Cloud Example</button>
  <button id="loadLoginExample" type="button">Load Login Example</button>
  <button id="discoverPhrasesBtn" type="button">Discover Phrases</button>
  <button id="nextToPhrasesBtn" type="button">Next: Phrases</button>
</div>

<pre id="scenarioOut"></pre>

<div class="cpux-card">
  <h4>WordPress ISC Phrase API Import</h4>

  <label>Phrase API endpoint</label>
  <input id="phraseApiEndpoint" value="https://keybytesystems.com/wp-json/isc/v1/phrases" />

  <label>Optional space_uid</label>
  <input id="phraseApiSpaceUid" placeholder="gcp_architect_field_language_001" />

  <button id="importPhrasesBtn" type="button">Import from API</button>

  <pre id="phraseImportOut"></pre>
</div>

<div class="cpux-card">
  <h4>Add phrase manually</h4>

  <label>Phrase</label>
  <input id="newPhraseText" placeholder="Example: reduce idle cost" />

  <div class="cpux-grid">
    <div>
      <label>SR Type</label>
      <select id="newSrType"></select>
    </div>
    <div>
      <label>Execution Potential</label>
      <select id="newExecutionPotential"></select>
    </div>
    <div>
      <label>IS Role</label>
      <select id="newIsRole"></select>
    </div>
    <div>
      <label>TV</label>
      <select id="newTv">
        <option value="Y">Y</option>
        <option value="U">U</option>
        <option value="N">N</option>
      </select>
    </div>
  </div>

  <button id="addPhraseBtn" type="button">Add Phrase</button>
</div>

<div id="phraseTable"></div>

<div class="cpux-row">
  <button id="backToScenarioBtn" type="button">Back</button>
  <button id="nextToDesignBtn" type="button">Next: CPUX Design</button>
</div>

<div class="cpux-grid">
  <div>
    <label>IC ID</label>
    <input id="icId" value="IC_cloud_architecture_resolution" />
  </div>
  <div>
    <label>CPUX ID</label>
    <input id="cpuxId" value="CPUX_architecture_resolution_001" />
  </div>
</div>

<div class="cpux-grid">
  <div class="cpux-slot">
    <h4>Incoming Signal</h4>
    <textarea id="incomingSignal">analyze_architecture_situation</textarea>
  </div>
  <div class="cpux-slot">
    <h4>O_holder</h4>
    <textarea id="holderObject">O_situation_holder</textarea>
  </div>
  <div class="cpux-slot">
    <h4>DN</h4>
    <textarea id="designNode">DN_architecture_reasoner</textarea>
  </div>
  <div class="cpux-slot">
    <h4>O_reflector</h4>
    <textarea id="reflectorObject">O_decision_reflector</textarea>
  </div>
  <div class="cpux-slot">
    <h4>Emitted Signal</h4>
    <textarea id="emittedSignal">emit_architecture_recommendation</textarea>
  </div>
</div>

<div class="cpux-card">
  <h4>Generate simple CPUX from phrases</h4>
  <p class="cpux-hint">
    This lightweight generator does not call an LLM. It uses current phrase roles to populate a draft CPUX structure.
  </p>
  <button id="generateDesignBtn" type="button">Generate Draft Design</button>
  <pre id="designOut"></pre>
</div>

<div class="cpux-row">
  <button id="backToPhrasesBtn" type="button">Back</button>
  <button id="nextToVerifyBtn" type="button">Next: Verification</button>
</div>

<button id="runVerifyBtn" type="button">Run Verification</button>

<div id="verifyList"></div>

<div class="cpux-row">
  <button id="backToDesignBtn" type="button">Back</button>
  <button id="nextToExportBtn" type="button">Next: Export</button>
</div>

<div class="cpux-row">
  <button id="buildExportBtn" type="button">Build Export</button>
  <button id="downloadJsonBtn" type="button">Download JSON</button>
  <button id="downloadMarkdownBtn" type="button">Download Markdown</button>
  <button id="clearDraftBtn" type="button">Clear Local Draft</button>
</div>

<pre id="exportOut"></pre>

<div class="cpux-row">
  <button id="backToVerifyBtn" type="button">Back</button>
</div>

Simplification Notes

This static component intentionally avoids a heavy backend dependency.

• Authentication is delegated to the WordPress ISC Phrase API when importing phrase collections.
• Phrase discovery is rule-assisted in this page; the LLM step can be added later.
• CPUX synthesis is draft-oriented, not final runtime generation.
• Verification checks are lightweight invariants, suitable for early authoring discipline.
• Export produces a portable seed that can later feed a full CPUX engine.

Suggested Next Step

Use the Phrase Collector API first to build phrase spaces. Then use this CPUX Authoring Tool to pull a phrase space into a design session and shape it into an IC / CPUX draft.