Causance

Company

About Causance.

Causance is the current platform and market identity for the governed software-delivery platform historically developed under the Agentic SDLC name. They are not separate products.

Causance is the platform and market identity. Lockheed & Co LLC is the parent company. Product, model, research, customer, and downstream evidence retain separate authority.

PLATFORM IDENTITY

One platform. A traceable technical lineage.

Use Causance for the current platform and market identity. Agentic SDLC remains the historical and technical identifier wherever canonical repositories, schemas, provenance records, exact evidence citations, or implementation identities still use it.

The transition does not create two products and does not justify silently renaming historical evidence.

PARENT COMPANY

Lockheed & Co is the parent company.

Lockheed & Co LLC is the parent company behind Causance. This property is the dedicated public home for Causance; the Lockheed & Co website describes the wider company and its other work.

Causance branding does not change the ownership, evidence, contracting, or governance status recorded by the sources that own those facts.

CATEGORY THESIS

Software Authority is a proposed discipline.

Software Authority is the proposed discipline for controlling who or what may change software, under what bounded conditions, with what required evidence, and through what review and recovery path.

It is a category thesis, not a claim that an analyst category, standard, regulated discipline, buyer budget line, or market consensus already exists.

SOFTWARE AUTHORITY MODEL

SAM is proposed and non-normative.

The Software Authority Model (SAM) is a separately governed proposed, non-normative model for making authority over consequential software change explicit. Lockheed & Co LLC retains the ownership and final ratification authority described by the current SAM governance direction.

Current SAM state does not establish a ratified standard, certification regime, conformance regime, appointed independent governing council, or automatic organizational-adoption claim. Technical review and future commercial programs do not create those statuses by implication.

RESEARCH PROGRAM

Assurance Continuity and Trust is research, not product certification.

Assurance Continuity and Trust is the current commercial name for the Lockheed & Co research program whose canonical repository and historical artifacts retain the Assurance Continuity identity. The program investigates when software-assurance evidence remains attributable through change.

The research remains a hypothesis under active investigation. It does not establish Causance superiority, universal applicability, safety, correctness, customer outcomes, certification, or product validation.

DOWNSTREAM EVIDENCE

A downstream implementation does not redefine the platform.

Technology Control Room and other downstream or reference implementations may provide evidence about their own bounded behavior. That evidence can be useful without being promoted into reusable Causance platform truth.

The same boundary applies to customer implementations: what is demonstrated downstream remains attributable to the scope that produced it unless a separate reusable evidence process supports a broader claim.

PRODUCT STATE

Product state is governed separately from the brand.

The Causance website describes the platform, its lineage, and the authority objects around it; it does not set product maturity, availability, licensing, or engagement status.

Current public maturity and availability boundaries are maintained on Evidence & scope. Customer execution, controlled evaluations, licensing, implementation, and other commercial actions require the separate authority that governs those actions.

CONVERSATION SCOPE

Start by naming which authority object you are asking about.

A platform question, Software Authority category question, SAM question, research question, company/commercial question, and customer-engagement question can require different evidence, disclosure, and decision authority.

Keeping those distinctions visible is part of the evidence and authority discipline: a useful answer should not borrow authority from a neighboring program merely because the names are related.