Testing environment
Launch the political-strategy Interface Lab
Use the live testing environment to pressure-test the engine through strategic modes, adaptive briefs, tension sliders, and visible tradeoff output. This is the fastest way to feel where the system is strong, thin, useful, or ornamental.
Albert Capability Manual
Current system-level reference for what is operational, what is merely scaffold, what has been validated, and where the real command surface exists today.
Capabilities
16
Integrated across strategy, CRM, messaging, web, memory, monitoring, and recovery
Corpus rows
193
Current political-strategy book metadata rows after cleanup
Embedded chunks
50,571
Local index built and retrieval-usable
Eval result
12.7/13
Average score for the local+Sonnet strategy pipeline over 20 questions
  • Political-strategy engine moved from scaffold retrieval to a real local+Sonnet recommendation path.
  • 20/20 evaluation questions now produce recommendation, tradeoff, and first-7-days sections.
  • Owned books are no longer treated as usable corpus assets unless ingestible text exists.
  • Main remaining weakness: source concentration around Lee Kuan Yew / Kissinger / Cromwell clusters.

Executive map

The system is best understood as perception, judgment, and execution linked by persistent memory and operational tooling.

Perception

  • User requests
  • Political corpus
  • CRM records
  • Memory and wiki notes
  • Dashboard and service state

Judgment

  • Problem structuring
  • Local retrieval and source-pack building
  • Sonnet synthesis
  • Tradeoff and recommendation logic
  • Evaluation harnesses

Execution

  • Reports and PDFs
  • Emails and broadcasts
  • CRM schema and workflows
  • Website deployment
  • Backups, dashboards, and recovery

Capability inventory

Political Strategy Intelligence Assistant

Now operational as a two-stage engine: local Qwen retrieval/source-pack generation followed by Sonnet synthesis into actual strategic options and recommendations.

Strength
Validated on 20 questions with 12.7/13 average and 20/20 recommendation outputs.
Current limit
Source diversity is still narrower than ideal in weaker cases.

Political Strategy Source Accumulation

Rebuilt around ingestibility, not store ownership. Books, journals, reports, speeches, and postmortems are now treated as different source classes.

Strength
Clear doctrine-gap-driven sourcing policy and efficient sourcing workflow now exist.
Current limit
No live per-source operational ledger yet.

Attio CRM

API-first operational CRM for political, donor, advocacy, and event structures.

Strength
Schema is live and tailored to the Australian political context.
Current limit
Views, pipelines, and live data import still need further work.

Canary Marker + Email

Leak-attributable broadcasts and programmatic email handling are operational.

Strength
Tested end-to-end with encrypted maps.
Current limit
Operational/legal use still requires judgment.

Websites + Intake Infrastructure

Cloudflare Pages and Workers provide autonomous website and form deployment.

Strength
Operational deployment pipeline with analytics and KV-backed forms.
Current limit
Domain purchase still has a manual CAPTCHA step.

Memory + Knowledge

Persistent local semantic memory, wiki compilation, and long-term continuity.

Strength
Zero API-cost memory with semantic recall.
Current limit
Quality still depends on disciplined capture.

Observability + Recovery

Grafana, Prometheus, Loki, watchdogs, and backup protocols now run with much better discipline.

Strength
Current-work state and cost semantics are far more truthful than before.
Current limit
More domain-specific panels can still be added.

Payments + Donation Flow

Stripe architecture exists but still isn’t fully deployed live end-to-end.

Strength
Products, links, and CRM-side model are configured.
Current limit
Webhook worker still not live.

Print & Physical Output

Print-ready PDFs, decks, and reports can be generated for real-world use.

Strength
Operational report/deck rendering paths exist.
Current limit
Printer-device control is still not explicitly integrated/documented.