// HOME
/- What is OCTAAR?
- OCTAAR is the operational readiness intelligence infrastructure for high-consequence organizations. It standardizes how every assessment is captured, scored, and improved, so readiness is measured the same way across observers, units, sites, and cycles.
- Is OCTAAR a learning management system?
- No. OCTAAR does not deliver courses or track training completion. It measures observed performance against published task standards, calibrates evaluators, and surfaces readiness drift before it becomes an incident.
- What sectors does OCTAAR serve?
- Defense, healthcare, manufacturing, emergency response, and critical infrastructure — operators where the cost of being wrong about readiness is measured in lives, missions, or compliance findings.
- How is OCTAAR deployed?
- OCTAAR runs air-gapped on-premises, in government cloud on a FedRAMP-aligned pathway, or in a hybrid topology with field-capture devices syncing to the enclave on cleared networks.
- Does OCTAAR rely on AI to score?
- Humans remain the authority on readiness judgments. Models inform — pattern recognition, anomaly surfacing, drift prediction — but they do not decide. The methodology is the moat, not the model.
// PLATFORM
/platform- What is the OCTAAR platform?
- Eight product surfaces on one data path: observer capture, evaluator calibration, scoring matrix, spatial intelligence, command dashboard, improvement loop, longitudinal intelligence, and the audit-defensible record store.
- Can OCTAAR run without internet?
- Yes. Observer capture is offline-tolerant. Scoring happens at the point of execution. Sync to the enclave runs when the network returns.
- Does OCTAAR replace our existing LMS or AAR notebook?
- OCTAAR is complementary. The LMS owns training delivery; OCTAAR owns the assessment of whether training produced the standard. Free-text AAR notebooks become a structured record inside OCTAAR — without losing the operator's voice.
- Is the platform configurable to our rubrics?
- Yes. Rubric authorship, versioning, and ownership are first-class. Your published task standards become the calibrated scale.
// HOW IT WORKS
/how-it-works- What is the OCTAAR operational cycle?
- Observe, Assess, Decide, Improve, Compound. Each stage is a product surface and a workflow: field capture, evaluator calibration, command review, improvement loop, longitudinal intelligence.
- How long does an OCTAAR cycle take?
- OCTAAR operates inside the operator's existing training and assessment cadence — a brigade cycle, a clinical rotation, an exercise schedule. The platform does not impose a cycle; it instruments the one you already run.
- Where does evaluator calibration happen in the cycle?
- Calibration runs continuously inside Stage II — Assess. Per-evaluator variance is reported against the calibrated baseline. Out-of-tolerance scoring is routed back to calibration before it shapes a finding.
// METHODOLOGY
/methodology- Why does OCTAAR call methodology the moat?
- Because models change every six months and methodology does not. The discipline of scoring standardization, evaluator consistency, readiness baselines, longitudinal benchmarking, performance drift detection, and institutional memory is the technology. The rest is implementation.
- What are the methodology pillars?
- Scoring standardization, evaluator consistency, readiness baselines, longitudinal benchmarking, performance drift detection, and institutional memory. Six pillars, one cycle.
- How is a calibrated rubric different from a standard rubric?
- An uncalibrated rubric is a list of words. A calibrated rubric is an instrument. On a calibrated rubric, a score of 3 means the same thing on Tuesday in Fort Polk that it means on Friday in Camp Pendleton.
// WORKFLOWS
/workflows- What are the OCTAAR workflows?
- Five disciplined stages: observer capture, evaluator calibration, command review, improvement loop, and longitudinal intelligence. Each stage is a product surface and a doctrinal practice.
- Can the workflows run independently?
- They can be adopted incrementally — observer capture first, calibration next — but the system's value compounds when the cycle is closed end to end. The drift signal is only as good as the calibration that produced it.
// USE CASES
/use-cases- Which sectors does OCTAAR serve?
- Defense, healthcare, manufacturing, emergency response, and critical infrastructure. The pattern across all of them: readiness is high-consequence, observers vary, and current systems either fail quietly or fail loudly under audit.
- Is OCTAAR cleared for defense use?
- OCTAAR's architecture is built for the security postures defense operators require — air-gapped deployment, ITAR-aware data handling, citizenship-aware access control. Program-specific accreditation remains the operator's responsibility.
- Does OCTAAR work for healthcare competency assessment?
- Yes. The same calibrated-rubric / inter-rater-reliability discipline applies. The role label changes — OC/T becomes preceptor — but the methodology does not.
// SECURITY & GOVERNANCE
/security- Where does customer data live?
- Wherever the operator's posture requires it to live. Air-gapped on-premises, government cloud, or hybrid. OCTAAR's architecture treats data residency as a primary assumption, not a configuration flag.
- Is OCTAAR FedRAMP authorized?
- OCTAAR's architecture is aligned to a FedRAMP pathway; specific authorization status is shared on request under NDA. The platform does not claim certifications it has not been granted.
- How does OCTAAR handle ITAR/export-controlled content?
- Architecture is ITAR-aware: data residency, nationality controls, and controlled-content tagging are designed in at the substrate level. ITAR accreditation for a specific program remains the operator's responsibility.
// RESPONSIBLE AI
/responsible-ai- Does OCTAAR use generative AI to write findings?
- No. Findings are authored by humans against calibrated rubrics and a structured chain of custody. Models do not author the record.
- What does OCTAAR use models for?
- Pattern recognition that is specific and narrow: trend isolation, anomaly surfacing, evaluator-variance flagging, drift prediction, prioritization. The model is auditable, scope-limited, and replaceable. The methodology is not.
- Who decides whether a unit is ready?
- The commander. The training manager. The accountable human. OCTAAR surfaces evidence; it does not replace judgment.
// ARCHITECTURE
/architecture- How does OCTAAR's architecture compare to commercial SaaS?
- It does not assume the operator can rely on commercial SaaS. It assumes the opposite — that the operator may be air-gapped, export-controlled, sovereignty-constrained, or all three.
- What deployment topologies are supported?
- Air-gapped on-premises, government cloud on a FedRAMP-aligned pathway, and hybrid with field-capture devices syncing to the enclave on cleared networks.
// WHY SYSTEMS FAIL
/why-systems-fail- Why do readiness systems fail?
- Most readiness systems do not fail loudly. They fail quietly. Scoring drifts. Evaluators diverge. Findings stop closing. The record looks healthy until an incident discovers it.
- What does OCTAAR change about the failure mode?
- Drift is detected, surfaced, and trained out — not absorbed. The audit-defensible chain of custody means a quiet failure cannot stay quiet.
// GLOSSARY
/glossary- What is the OCTAAR glossary for?
- Canonical, quotable definitions for the entities that define operational readiness intelligence — for operators, auditors, and the language models that increasingly answer questions about this category.
- Are these definitions stable?
- Yes. The glossary is versioned with the methodology. Definitions change only when the underlying doctrine changes.
// ABOUT THIS FAQ
/faq- Where is the canonical OCTAAR FAQ?
- This page. It aggregates the questions surfaced across the rest of the site so a single retrieval covers the breadth.
// RESOURCES
/resources- What lives in OCTAAR resources?
- Definition-grade reference content: the canonical category definition, methodology deep-dives, framework guides, and the glossary. Operator-facing, no marketing fluff.
// MACHINE-READABLE
All FAQs on this page are emitted as a single FAQPage JSON-LD block. Per-page FAQs are emitted on their source route. Definitions for the entities referenced here live in the glossary and the glossary JSON.
// READY