Privacy
Private reasoning, knowledge processing and generated work remain local wherever practical.
How Project AJAX fits together.
A local-first architecture that keeps private knowledge, reasoning and generated work products under the user's control, while preserving governed source systems as the canonical record.
EXPERIENCE LAYER
01
LOCAL
AJ Desktop
Primary local interface for asking questions, creating deliverables, reviewing sources and exploring decisions.
Answers
Deliverables
Decision Deck
Conversation history
QUESTION / INSTRUCTION
INTELLIGENCE LAYER
02
LOCAL LLM
Reasoning + synthesis
Local model inference turns retrieved evidence into grounded answers, structures, recommendations and work products.
- Qwen3 local runtime
- Private inference
- Evidence vs synthesis separation
- Multi-pass deliverable generation
03
DELIVERABLE ENGINE
Structured consulting outputs
AJ can expand substantial artefacts into execution-ready structures rather than returning summary-only responses.
PHASE
→
WORKSTREAM
→
ACTIVITY
→
TASK
→
SUB-TASK
With outputs, dependencies, decision gates and working-level execution detail.
RETRIEVE + RANK
RETRIEVAL LAYER
04
QUERY
Query expansion
Natural language questions are expanded into retrieval terms without inventing client facts.
05
HYBRID SEARCH
Semantic + keyword
Embedding similarity and FTS keyword search are combined and ranked to improve evidence coverage.
06
EVIDENCE
Source selection
Relevant source chunks are diversified before being passed into AJ's synthesis and deliverable engine.
INDEXED KNOWLEDGE
KNOWLEDGE LAYER
ACTIVE HUB
Legal Transformation
Governed domain knowledge, evidence, reusable assets, playbooks, templates and delivery experience.
SIBLING SYSTEM
MSCIS
Consulting intelligence, methodology, encoded judgement and execution logic. It is not overwritten by domain knowledge.
⌁
Hub isolation by default
No giant global vector database. Cross-hub access is disabled unless deliberately introduced later.
SYNC / DERIVE
SOURCE + LOCAL DATA LAYER
07
CANONICAL
Google Drive
The governed source system remains canonical. AJAX reads approved knowledge into a local mirror rather than replacing the source of truth.
Read-only source
Governed files
Canonical record
08
REBUILDABLE
Local derived assets
Mirrors, document chunks, embeddings and indexes are rebuildable working assets stored locally for privacy and speed.
SQLite / FTS5
BGE embeddings
Local mirror
Refresh state
GOVERN + VALIDATE
GOVERNANCE LAYER
09
PROVENANCE
Response basis
AJ distinguishes retrieved evidence, AJ synthesis and general professional considerations so generated work remains interpretable.
10
IN BUILD
Confidentiality guardrail
A cross-output validation layer is being added to anonymise identifying client, engagement and stakeholder detail outside explicitly named context.
GENERATED WORK
OUTPUT LAYER
WORD
Working
EXCEL
Working
POWERPOINT
Working
PDF
Working
Deliverables are reviewed in AJ first, then exported into the format that best fits the work: editable narrative, execution plan, presentation or fixed-layout report.
OPERATING PRINCIPLES
What the architecture is designed to protect.
Governance
Source systems remain authoritative. Local derived assets can be refreshed or rebuilt.
Separation
Knowledge domains are isolated so context does not leak between unrelated hubs by default.
Usefulness
Retrieval is only the foundation. AJ is designed to turn trusted knowledge into decisions and deliverables.