FAQs

Organizations naturally ask practical questions about scope, operation, governance, and fit.

These questions reflect a deeper concern:
Can alignment actually be sustained as systems, policies, and AI evolve?

The following FAQs address how OrcaEIS operates and how it integrates into real enterprise environments—without relying on assumptions, one-off interventions, or vendor lock-in.

Understanding OrcaEIS

1. What is OrcaEIS, in simple terms?

OrcaEIS is Enterprise Alignment Infrastructure.

It is designed to continuously establish what should be true, observe authoritative evidence describing what is actually true, determine whether those states align, govern an appropriate response when they do not, and verify whether the resulting action restored alignment.

Strategic Intent ↔ Operational Reality

That's Continuous Enterprise Alignment.

2. What is Strategic Intent?

Strategic Intent represents the required state of the enterprise.

It may be derived from strategy, policy, regulation, contractual obligations, security requirements, operating standards, approved configurations, risk tolerances, mission requirements, business rules, or authorized decisions.

It answers:

What should be true?

3. What is Operational Reality?

Operational Reality is the observed state of the enterprise, established from authoritative evidence.

That evidence may exist across identity systems, HR platforms, ERP and CRM systems, learning platforms, cloud environments, security tools, workflow systems, configurations, AI systems, and other operational sources.

It answers:

What is actually true?

4. Why isn't this just another monitoring or observability platform?

Monitoring tools show events and system behavior. OrcaEIS is being designed to relate that evidence to approved requirements and dependencies, explain meaningful gaps, support an authorized response, and verify the resulting outcome. The distinction is the governed alignment loop across evidence sources.

5. Is OrcaEIS an AI Governance Platform?

AI governance is one important application of Enterprise Alignment, but it does not define the boundary of OrcaEIS.

OrcaEIS is designed to evaluate alignment across people, systems, workflows, policies, controls, configurations, data, and AI.

An AI governance requirement can become Strategic Intent.

Observed AI behavior, permissions, configurations, actions, and outcomes can become Operational Reality.

OrcaEIS evaluates the relationship between them.

6. Does OrcaEIS replace existing enterprise systems?

No.

Your ERP remains your ERP.

Your CRM remains your CRM.

Your IAM remains your IAM.

Your HRIS, LMS, ITSM, SIEM, CMDB, cloud platforms, security systems, and operational applications continue performing their specialized functions.

OrcaEIS is designed to establish relationships across the authoritative evidence those systems provide.

How it Works

7. What does "behind-the-login" mean?

Much of Operational Reality exists inside authenticated enterprise environments rather than in public documentation or periodic reports.

OrcaEIS is designed to use scoped, authenticated, primarily read-only connections to observe the evidence necessary to establish relevant enterprise state.

The principle is:

Observe reality where the work actually happens—while minimizing access and preserving system authority.

8. Does OrcaEIS copy all of our enterprise data?

It should not need to.

OrcaEIS is designed around evidence minimization: observe or retain the information necessary to establish an alignment condition rather than indiscriminately ingesting everything an enterprise possesses.

The required evidence depends on the alignment problem being evaluated.

9. What happens when OrcaEIS identifies misalignment?

A finding should establish:

which requirement is affected;
what authoritative evidence demonstrates the divergence;
which people, systems, processes, controls, or artifacts are affected;
relevant dependencies and potential impact;
confidence in the finding; and
provenance supporting the conclusion.

OrcaEIS can then support an appropriate governed response.

10. Does OrcaEIS automatically fix problems?

Not by default.

The architecture separates capability from authority.

OrcaEIS may identify, simulate, recommend, generate, or eventually execute corrective actions, but consequential actions remain bounded by governance, risk, confidence, scope, and appropriate human authority.

Autonomy can expand as trust is demonstrated.

It can contract when confidence or governance performance deteriorates.

11. What does "Governed Autonomy" mean?

Governed Autonomy means AI can operate independently within explicitly authorized boundaries.

A typical trust progression may look like:

Observe → Explain → Recommend → Approve → Act Within Bounds → Verify → Learn

The objective is not autonomous action for its own sake.

The objective is trustworthy autonomy supported by evidence, governance, provenance, and continuous verification.

12. Does OrcaEIS know whether a corrective action worked?

It checks again.

OrcaEIS does not treat execution as proof of success.

After an approved response occurs, Operational Reality is observed again and compared with the required state.

The result may be:

ALIGNMENT RESTORED

or:

MISALIGNMENT REMAINS

That outcome becomes evidence for the next alignment cycle.

AI, Trust, & Governance

13. Where does AI fit into OrcaEIS?

AI can assist with interpretation, reasoning, prediction, simulation, artifact generation, impact analysis, and recommended responses.

But critical alignment determinations should remain grounded in authoritative enterprise evidence and governed rules rather than relying solely on probabilistic AI judgment.

OrcaEIS is designed to remain model- and platform-agnostic.

14. What happens when AI itself needs to be governed?

AI becomes part of Operational Reality.

Its identity, authority, permissions, applicable policies, actions, dependencies, outputs, and outcomes can become evidence evaluated against Strategic Intent.

The same alignment principle applies:

What is the AI authorized and required to do?

versus:

What is it actually doing?

15. How does OrcaEIS approach trust?

Trust is not assumed simply because a system performed correctly once.

The broader OrcaEIS architecture is designed around evidence, confidence, provenance, outcome verification, governed authority, and continuous testing of governance performance.

Greater demonstrated trust can support greater autonomy.

Degraded confidence can trigger reduced autonomy and increased human oversight.

16. Can OrcaEIS explain why it reached a conclusion?

Explainability and provenance are foundational architectural requirements.

A meaningful alignment finding should be traceable to the evidence, requirements, system state, governance conditions, and relevant transformations that produced it.

The objective is not:

“The AI says you're misaligned.”

It is:

“Here is the requirement. Here is the observed evidence. Here is the divergence. Here is why it matters. Here is how we reached the conclusion.”

Platform & Engagement

17. What are OrcaPMO and SmartLMS?

OrcaPMO is being built to coordinate delivery through approved plans, observed execution, dependencies, readiness and governed decisions.

SmartLMS is being developed to turn Word and PDF procedures and imported screenshots into role-specific training and job aids, with source references, review, version history and branded exports.

Both are in development. They are focused products within the wider OrcaEIS vision; the full suite is not yet generally available.

18. Is OrcaEIS only about training?

No.

Our current product focus spans project delivery with OrcaPMO and procedure-based training with SmartLMS. Both are in development.

The same alignment pattern can potentially apply to identity and access, AI governance, enterprise modernization, compliance, security controls, operational readiness, post-implementation stabilization, and other domains.

Change the requirement.

Change the evidence.

Change the systems.

The alignment architecture remains.

19. Is OrcaEIS already a fully deployed autonomous enterprise platform?

No. OrcaEIS describes a broader architectural vision, with OrcaPMO and SmartLMS currently in development.

The Orca Suite is a phased roadmap. Individual product scope, availability and integration capabilities will be stated separately as each release is verified.

We welcome design-partner conversations around a bounded operational problem. Expressing interest does not create an account or start a trial.

20. What is AEIS?

AEIS is the Autonomous Enterprise Intelligence System, the enterprise-intelligence foundation of the OrcaEIS architecture.

It is designed to establish evidence-backed enterprise truth by observing and relating operational evidence across systems, identities, permissions, configurations, workflows, dependencies, and other enterprise entities.

In simple terms:

AEIS helps establish what is actually true.

21. What is SITORA?

SITORA stands for Strategic Intent → Operational Reality Alignment.

It is the alignment architecture responsible for evaluating observed Operational Reality against applicable Strategic Intent and determining whether the enterprise remains within its required state.

In simple terms:

SITORA determines whether what is true aligns with what should be true.

22. What makes OrcaEIS defensible?

OrcaEIS is supported by an 11-filing patent-pending portfolio spanning interlocking capabilities across enterprise observation, truth modeling, strategic alignment, governance, prediction, simulation, autonomous execution, outcome verification, learning, provenance, federated verification, adversarial governance testing, and independent oversight.

The individual inventions matter.

The architecture they form together matters more.

23. How can an organization explore OrcaEIS?

Start with one meaningful alignment problem.

Identify: