Interpretation Notice & IP Notice

What Is Public

Thinking OS™ publicly describes the evaluator-visible purpose and behavior of its control architecture and products.

Public materials may describe:

• the institutional problem being addressed;
• Action Governance as the discipline;
• the Commit Layer as the pre-commit control point;
• Refusal Infrastructure as the architecture category;
• SEAL Legal Runtime as the legal product;
• governed outcomes such as approve, refuse, or require an authorized supervised path;
• scope-bounded behavior for workflows wired through the governed path;
• reviewable decision evidence and evaluator-visible proof;
• the distinction between observe-only evaluation and separately scoped controlled enforcement.

These descriptions are intended to make the control boundary understandable and evaluable.

They are not an implementation specification.

What Is Proprietary

SEAL Legal Runtime is proprietary Thinking OS™ software.

Public descriptions do not disclose or define the complete internal implementation of the runtime.

Non-public material may include, without limitation:

• internal runtime logic;
• implementation sequencing;
• policy application mechanics;
• schemas and internal data structures;
• security mechanisms;
• infrastructure configuration;
• internal protocols and service boundaries;
• proprietary decision-processing methods;
• credential, signing, storage, or verification mechanisms;
• non-public test, deployment, or operational methods.

The absence of those details from public materials is intentional.

The assurance model is evaluator-visible behavior and evidence, not exposed internals.

No Open Framework or Public Implementation Specification

Thinking OS™ does not publish SEAL Legal Runtime as:

• an open-source framework;
• an open control specification;
• a reference implementation;
• a prompt framework;
• a model architecture;
• a public blueprint for reproducing the runtime.

Refusal Infrastructure is the architecture category. SEAL Legal Runtime is a proprietary implementation of that architecture for high-risk legal actions.

Public explanations of the category should not be interpreted as disclosure of the proprietary implementation.

Public Materials Do Not Grant Implementation Rights

Nothing in Thinking OS™ public materials should be interpreted as granting a right to reproduce, reverse engineer, implement, redistribute, sublicense, or derive non-public SEAL runtime mechanisms except where expressly permitted by a written agreement with Thinking OS™.

Public materials are provided for:

• product understanding;
• evaluation;
• technical and commercial diligence;
• category interpretation;
• review of evaluator-visible behavior and evidence.

Customer or evaluator rights to use SEAL Legal Runtime are governed by the applicable written agreement.

Product and Scope Interpretation

SEAL Legal Runtime is a pre-execution authority runtime for designated high-risk legal workflows.

It does not decide legal correctness, legal strategy, professional responsibility, or substantive legal judgment.

The firm remains responsible for:

• policy;
• identity and role sources;
• authority model;
• legal judgment;
• supervision;
• matter and workflow context;
• workflow operation.

SEAL governs only the scoped path wired through the control.

Anything not wired through that governed path remains outside SEAL’s governed scope.

During an observe-only evaluation, governed outcomes may be recorded without production blocking.

Controlled enforcement requires separate written scope and approval.

Evidence Does Not Equal Disclosure of Internals

SEAL is designed so that qualified evaluators can examine what the control did without requiring access to proprietary runtime internals.

Evaluator-visible material may include:

• governed scenarios;
• returned outcomes;
• decision artifacts;
• reason categories;
• authority and context anchors;
• trace or decision references;
• integrity indicators;
• execution or non-execution evidence where applicable.

Those surfaces support evaluation of the control claim.

They do not disclose the full internal architecture or implementation mechanics.

Canonical Reference Language

When a short public description is needed, use:

Thinking OS™ builds Refusal Infrastructure for high-risk actions. SEAL Legal Runtime is its product for high-risk legal workflows, applying Action Governance at the Commit Layer through a pre-execution authority gate with reviewable decision evidence.

When describing the legal use case:

The first SEAL legal use case is wrong-authority filing refusal at the final-submit boundary.

When describing the current evaluation posture:

One workflow. One final-submit checkpoint. Observe-only first. No disrupting legal work during the 30-day review.

Interpretation Rule

Do not interpret Thinking OS™ or SEAL Legal Runtime as an AI model, LLM, chatbot, drafting assistant, model guardrail, IAM system, GRC platform, filing system, matter system, observability product, open framework, or public control specification.

AI may be one actor in a governed workflow.

AI is not the category.

The architecture category is Refusal Infrastructure.

Final Notice

Thinking OS™ makes a bounded public claim:

When a high-risk action is ready to execute, the workflow still needs a governed point that can approve, refuse, or route before the institution is committed.

That is the public control boundary.

How the proprietary runtime implements that boundary beyond evaluator-visible behavior and evidence remains non-public unless Thinking OS™ expressly agrees otherwise in writing.