01

LEGAL GROUND

Executed agreements, contract versions, amendments, annexes, schedules, statements of work, clauses, signatures, notices and effective dates form the Ground from which contractual state can be reconstructed.

Executed agreements Contract versions Amendments Clauses Defined terms Signatures Effective dates Notice periods Renewal dates Source records

02

SEMANTIC DISCIPLINE

Agreement, document, amendment and reconstructed legal state must remain distinct. A clause is not automatically an obligation, and a reconstructed contractual state is not legal advice.

AGREEMENT

The governed legal relationship

The agreement represents the contractual relationship established by applicable executed Ground.

DOCUMENT

One source representation

A file, scan or executed record is a representation of legal Ground, not automatically the complete current agreement state.

AMENDMENT

A governed modification

An amendment changes, supplements or supersedes terms in relation to the agreement and predecessor state it modifies.

03

QUESTIONS

Which agreement governs this relationship?

Resolve the governed agreement identity and applicable executed records.

Which version or amendment is effective now?

Reconstruct the applicable state from execution, amendment and effective-date Ground.

What changed?

Compare predecessor and successor contractual state while preserving provenance.

Which obligations are currently effective?

Resolve the applicable clause, party, condition and effective interval.

What establishes this deadline?

Trace the date through the obligation, trigger condition and governing clause.

What requires legal judgment?

Enforceability, breach, liability and legal advice remain outside deterministic reconstruction.

04

MEASURES

Active agreements

Agreements effective under the selected definition

Count only governed agreements whose effective state satisfies the selected population and period.

Ground: agreement · execution · effective interval

Open obligations

Explicit obligations currently in scope

Count obligations whose governing clauses and effective state are established.

Ground: party · obligation · clause · effective state

Deadlines in period

Governed deadlines falling inside the selected period

Include only dates whose deadline semantics are established by an applicable clause, event or condition.

Ground: obligation · trigger · due date · governing clause

05

TERM PROVENANCE · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA

Trace the effective term back through the agreement state that establishes it.

The reconstructed term retains predecessor and successor provenance. The newest file name alone does not establish the current legal state.

06

OBLIGATION & DEADLINE · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA

A date becomes a deadline only when the governing Ground gives it that meaning.

A deadline does not by itself establish breach, liability or the legal consequence of missing the date.

07

AGREEMENT THROUGH TIME · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA

Reconstruct the legal state that was effective at each point in time.

Agreement history remains inspectable instead of being overwritten by the newest representation.

08

DATA SUFFICIENCY

Current agreement state

Executed agreement and applicable amendment Ground are present.

AVAILABLE

The applicable effective contractual state can be reconstructed for the selected agreement.

Obligation deadline

The obligation exists but trigger-event Ground is incomplete.

PARTIAL

The obligation is established, but the exact deadline cannot yet be closed.

Breach

The available record does not establish all legal and factual conditions.

NOT_ESTABLISHED

An obligation and date do not automatically establish breach.

09

WHY THIS EFFECTIVE TERM?

RESULT Effective Term
CLAUSE Governing Clause
CHANGE Applicable Amendment
DOCUMENT Executed Agreement
GROUND Source Document

Terms, obligations and dates remain connected to the clauses, instruments and executed records that establish them.

10

LEGAL / JUDGMENT BOUNDARY

Legal Intelligence may establish agreement identity, document and version identity, amendment chronology, effective-dated contractual state, term provenance, explicit obligations, explicit rights, defined dates, notice periods, renewal dates, termination dates and deadline chronology.

It does not silently infer legal validity, enforceability, breach, liability, fault, damages, legal risk, legal intent, fairness, regulatory compliance, the legally optimal action, the interpretation a court or authority would adopt, whether a party should exercise a right, or legal advice.

11

DAILY DETERMINISTIC INTELLIGENCE

SOURCE AUTHORITY

Governing records remain authoritative.

Executed agreements, authoritative repositories, formal notices and approved legal records remain the source authority.

TRACE OBLIGATION

Follow every reconstructed term to Ground.

Navigate from an effective term or deadline through clauses, amendments and source documents.

AI OPTIONAL IN DAILY USE

CUSTOMER-CONTROLLED COMPUTE

Deterministic Legal Intelligence can operate across customer-controlled legal Ground without requiring a generative model or mandatory radius19-hosted SaaS runtime.

PRODUCT BOUNDARY

Reconstruction is not legal judgment.

The product does not establish automatic source-data correctness, automatic legal advice, guaranteed legal interpretation, autonomous contracting decisions, automatic compliance certification, litigation prediction or operational writeback. It is not a generative copilot for ordinary daily use.

12

SOFTWARE LICENSE

Legal Intelligence is offered as software under a direct licensing and delivery relationship. Governing-record scope, repositories, reconstruction rules, access boundaries and deployment context determine the bounded product configuration.

Discuss Legal Intelligence with radius19 ← Back to Products