Compass
The demand-intake analyser
StatusConceptProposed
Where it stands. A proposed concept, among the earlier tools. Not yet built.
01What it does
01
Resolves a signal into a bearing
A demand signal or an RfP becomes which Solution answers it and the instructions to stand it up; an opening or a contact becomes a hypothesis for how DAAC puts it to work.
02
Proposes; others deliver
Compass proposes the bearing, Mason renders the artefacts, and the other Tools deliver.
02Its place on the control plane
Compass sits on the propose plane: it turns a raw outside signal into a proposed response and writes nothing itself. Mason then renders the artefacts and the other Tools deliver. Its propose-plane peers are below.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- MasonFeedsDemand record, carried to Mason by a human today, the Proposition workflow names this a GAP
- ForgeFeedsDemand record, the App build workflow calls this the clearest instance of "propose→actuate arrows are human-carried"
- HelmConsumesDemand record, read by Helm/the maintenance seat to notice and dispatch build work
- CrawlFeedsDemand record, the Opportunity → Hub workflow: Compass senses demand → proposition → Crawl seeds the hub
- GimbalNamed as a pair, with no interaction specified yet.
04Where it does the work
Others on the propose plane