# Pascal Context Graph

Source: https://www.trypascal.io/platform/context-graph

Keep the decision. Remember why.

Preserve decisions with their evidence and history. Help the next person or agent understand the precedent, what changed, and what still applies.

## Capabilities

### Keep institutional memory

Retain useful decisions, lessons, and operating context beyond a single conversation.

### Follow the evidence

Connect a memory document to the sources and reasoning behind it.

### Review what is current

See review status and aging information before using a memory in new work.

### Connect related work

Bring relevant records, decisions, and prior outcomes into the same context.

### Use memory with care

Apply current access and source permissions when people or agents retrieve information.

### Learn from the outcome

Carry reviewed lessons into future assignments while keeping current source evidence authoritative.

## Connected context

Connect decisions to Compass cases and Atlas investigations. Use Dynamic Context to bring accessible, relevant precedents into the next assignment.

- Memory records, source citations, revisions, and review candidates
- Rationale, alternatives, owners, scope, and review dates
- Conflicts, replacement records, and access policy

## Controls and permissions

Review memory before treating it as current guidance. Source records still determine today’s facts, and a previous approval does not grant permission to repeat an action. Context Graph retains business rationale, not private model reasoning.

## Example

A team remembers that a weekly roster once justified carrier fallback. The agreement has since changed. Context Graph preserves the earlier policy, marks it as superseded, and links the current confirmed-capacity requirement to clause 7b, so useful history does not become stale advice.

## Workflow

### Recognize the superseded policy

- The earlier Horizon fallback policy remains inspectable. Its status and replacement link explain why it should no longer guide the decision.

### Follow the current requirement

- Clause 7b requires confirmed carrier capacity. A weekly roster by itself does not meet the current agreement.

### Inspect the cited passage

- Open the source wording beside the stored observation. The next reviewer can understand the basis for the requirement without rebuilding the investigation.

## Next steps

Choose a recurring decision and the evidence behind it. Define how the team will review, update, and recognize superseded knowledge.

- [Contact sales](https://www.trypascal.io/contact)
- [Pascal Work](https://www.trypascal.io/solutions/pascal-work)