Phrase Collector API Console

Cloud architects do not begin with resources. They begin with phrases:

“deploy my container”
“expose this service publicly”
“reduce idle cost”
“move this workload closer to users”
“make it survive a zone failure”

In Intention Space terms, these phrases are the earliest visible form of Situational Reality.
A collection of such phrases becomes an Intention Space instance. After collection, each phrase can be normalized and classified as an Intention, Design Node, Object, Pulse, Signal, CPUX, Constraint, Service, Resource, or Decision phrase.

This page talks directly to the WordPress-hosted Phrase API.

API Console

Connection

API Base URL

Cookie login works when the browser accepts the WordPress login cookie. For admin normalization, use a WordPress Application Password.

Optional API Authentication

WordPress username Application password

Leave blank to use browser cookie login. Fill these fields to use Basic Auth for create/update APIs.

Create Intention Space

Space UID Title Description

Spaces

Submit Phrase

Phrase Context Source Initial IS Role

Phrase List

Admin Normalization

Requires a WordPress admin account. Select a phrase from the list or enter its ID manually.

Phrase ID IS Role Normalized ID Normalized phrase Cluster description Status Admin note

API Flow

Create Intention Space
        ↓
Submit phrases into that space
        ↓
Admin normalizes phrase clusters
        ↓
Admin classifies phrases as I / DN / O / Pulse / Signal / CPUX
        ↓
Export space JSON
        ↓
Use as seed for CPUX design

Notes

User login is handled by WordPress.
Public read APIs can load spaces and phrases.
Create/update APIs require authentication.
Admin normalization requires a WordPress admin account or Application Password.
The exported JSON is intentionally shaped as an Intention Space seed rather than a plain phrase list.