Axonix Agentic Environment Workspace
Axonix Agentic Environment Workspace
This folder is the Axonix workspace layer for the Flowsign Agentic Environment.
It keeps Axonix-specific public research, source candidates, draft findings, PVP/PQS decisions, and review gates separate from accepted GTM truth. Research and method-lens outputs can guide hypotheses, but they do not become market-facing proof without source IDs, evidence weight, review owner, prior state, new state, and approval status.
Canonical Rules
Use these files first:
| Need | Source |
|---|---|
| Agentic Environment behavior | agentic-environment/v1/kernel.md |
| Runtime/source system boundaries | agentic-environment/v1/runtime-source-map.md |
| Source-card rules | agentic-environment/v1/registry/sources/README.md |
| Method lens boundary | agentic-environment/v1/registry/lenses/README.md |
| Jordan Crawford lens routing | agentic-environment/v1/registry/drilldowns/method-lens-router.md |
| Axonix source registry | clients/axonix/agentic-environment/source-registry.md |
| Axonix evidence register | clients/axonix/agentic-environment/EVIDENCE_REGISTER.md |
Workspace Principle
Axonix should move through:
Source intake -> evidence gate -> context object -> campaign/action -> market feedback -> finding -> weighted review -> accepted update -> growth lever candidate.
This packet stops before campaign/action. It creates source-backed hypotheses, a public-data target-account map, Pain-Qualified Segment mapping, and proto-PVP candidates for human review. No live vendor system, campaign, CRM, mailbox, automation, MCP config, hook, or credential is touched.
Current Truth State
| Area | Current state |
|---|---|
| Workspace status | Scaffold created for Axonix packet. |
| Source basis | Public web, public vault seed brief, and local Agentic Environment specs only. |
| Direct market feedback | None registered. |
| Campaign feedback | None registered. |
| Accepted proof points | None. |
| Accepted findings | None. |
| Accepted updates | None. |
| Runtime implementation | Not created. |
Evidence Boundaries
- Public website/domain/competitor/account research is supporting evidence only unless market response exists.
- PQS means Pain-Qualified Segment in this workspace.
- Jordan Crawford/Cannonball outputs are method-lens hypotheses until named-account public proof and market feedback validate them.
- A true PVP requires named-account, source-backed, public or approved data and must pass the PVP specification. Anything weaker stays labeled
pqs_hookorproto_pvp. - No accepted proof point or accepted update can be created without explicit source IDs, evidence weight, review owner, prior state, new state, and approval status.
Stop Conditions
Stop before:
- Launching or changing campaigns.
- Sending outreach or importing/exporting leads.
- Writing to Smartlead, Apollo, Gmail, Attio, Drive, Supabase, Trigger.dev, Resend, Lucidchart, Comfy, MCP configs, hooks, agents, credentials, or
.envfiles. - Treating public research or Axonix site copy as accepted market truth.
- Promoting an Axonix claim into market-facing proof without approval.
- Stating that Axonix and Eagle Eye are the same business unless public evidence is sufficient or the client confirms it.
