Companies

A company in ASUME is not a form you fill in or a page of stored facts.

It is a maintained understanding of one organization's current state, constructed from evidence and revised as that evidence changes.

At a simplified level, a company is the result of the process described in the Understanding section:

Company information → Evidence → Inference → Understanding

The company is the persistent representation that this process produces and keeps.

When you open a company, you are looking at what the available evidence currently supports about that organization, together with the basis on which those statements exist.

A company organizes what ASUME can establish about an organization into a structured understanding rather than a summary.

Depending on the available information, that structure can contain:

• structured statements about the company's needs, capabilities, constraints, and priorities;
• the evidence supporting those statements;
• the assumptions the reasoning depends on;
• relationships between propositions;
• uncertainty and competing explanations;
• temporal information and scope;
• and revision history.

Together, these represent what ASUME currently understands about the company and why it understands it that way.

A company is not the same as the company information ASUME is allowed to read.

Information is the input. Websites, product pages, job posts, documentation, announcements, and any granted internal sources are raw material.

The company is what ASUME reasons that information into: evidence for propositions about the organization's current state.

This distinction matters because two organizations can publish similar information while their underlying state differs, and because the same information can support different conclusions once it is interpreted.

A company therefore represents an interpretation of available information, not a copy of it.

ASUME does not reconstruct an organization from scratch every time you ask a question about it.

The company is a persistent object that subsequent reasoning operates on, as described in maintained understanding.

Once a belief about the company is established, it can remain part of the company understanding beyond the reasoning operation that produced it.

This is what allows repeated work on the same organization to stay consistent rather than producing a slightly different company each time.

It also means work compounds. Evidence gathered for one question remains available for the next.

A statement in a company retains its supporting evidence rather than becoming free-floating text.

Where the reasoning goes beyond what the evidence directly establishes, the relevant assumptions remain explicit.

For example, a company may maintain that an organization is expanding its implementation capability. That belief may depend on an assumption that observed hiring represents additional capacity rather than replacement.

Keeping evidence and assumptions attached to the statement is what makes a company inspectable rather than a set of assertions.

Because a company preserves its reasoning structure, it supports traceability.

From any statement, you can move toward its basis:

Belief → Proposition → Assumption → Evidence → Source

This lets you ask not only what ASUME represents about an organization, but why it represents it that way and what would need to change for the conclusion to change.

An organization does not remain the same, and neither does its company understanding.

New evidence can support an existing belief, weaken it, contradict it, introduce a new proposition, or make a previously relevant belief obsolete.

When that happens, ASUME revises the affected parts of the company rather than rebuilding it or silently overwriting the previous conclusion.

The revision is local: only components whose justification depends on the change need to be reconsidered, while unrelated beliefs remain intact.

A company therefore reflects what the evidence currently supports, and it carries the history of how that understanding changed.

A company is designed to be challenged, not just read. This is the role of verification.

A reviewer can inspect the evidence behind a statement, correct an extracted proposition, reject an assumption, introduce additional evidence, or compare competing explanations.

When a verified correction changes the basis of a belief, the company is revised accordingly.

Human review therefore does not sit beside the company as a separate comment. It can participate in the company's evolution.

ASUME maintains the company before applying a specific objective.

The same company can be evaluated for revenue, partnerships, procurement, investment, and other objectives without constructing a different organization for each.

Different objectives may emphasize different parts of the same company, but they operate on one shared, revisable representation.

This separation keeps objective-specific work from rewriting the underlying company state.

Individual companies are usually worked with in groups. Lists are how teams organize companies and reuse their maintained understanding across repeated work.

A list does not copy or freeze the companies it contains. It references the same maintained understanding, so companies stay current as their evidence changes.