Axiom Hub FAQs

Question 1

What is the 'Two-State Session Machine'?

Accepted Answer

This mechanism ensures AI agents cannot read files or write code until they've loaded context from previous sessions. It acts as a gate, guaranteeing that agents are always informed by the project's established architectural decisions.

Question 2

What problem does Axiom Hub solve for AI coding agents?

Accepted Answer

Axiom Hub solves the 'Week Seven Wall' problem, where AI coding agents make inconsistent architectural decisions across sessions, leading to contradictory codebases. It provides persistent memory and prevents these costly architectural drifts.

Question 3

How do developers interact with Axiom Hub's features?

Accepted Answer

While AI agents automatically capture decisions and load context, developers can use the interactive web dashboard to visualize all captured decisions, review contradictions, and formally resolve conflicts to maintain architectural integrity.

Question 4

How does Axiom Hub prevent architectural contradictions?

Accepted Answer

It enforces mandatory context loading, ensuring AI agents start with prior decisions. It also automatically detects conflicts between new proposed decisions and existing ones, surfacing them in a dashboard for developer resolution before they become bugs.

Question 5

Can Axiom Hub integrate with existing AI coding agent workflows?

Accepted Answer

Yes, Axiom Hub integrates via an MCP server. Once configured, it automatically manages context loading and decision capture, becoming a transparent but crucial layer in your AI-assisted development workflow.

Axiom Hub

Axiom Hub

主な機能

ユースケース

主な機能

ユースケース