# Pascal Dynamic Context

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

The right knowledge for the job at hand.

Package the knowledge a recurring job needs. Test which sources are included, see what permissions exclude, and keep the right versions within reach.

## Capabilities

### Build a library around real jobs

Create reusable knowledge packages for an investigation, team, or recurring assignment instead of assembling the same background every time.

### Combine the formats your work needs

Bring documents, business records, and structured knowledge into one package while keeping each item linked to its source.

### Choose the source precisely

Identify which collection, version, or record population belongs in the package. Make required information explicit.

### Compose company and task knowledge

Combine reusable organizational context with the more specific material needed by a team, application, or individual task.

### Apply permissions when context is used

Assemble knowledge for the current actor and workspace. A reusable package does not give its consumer new access rights.

### Inspect and improve the package

Test what the package includes, review missing or optional material, and keep changes versioned as the job evolves.

## Connected context

Assemble relevant records, documents, process context, and reviewed decisions from across Pascal. Reuse those packages in Agents, Workrooms, and applications under each participant’s current access.

- Context packages, source selections, audiences, and versions
- Connections to agents, Tasks, rooms, teams, and applications
- Test requests, citations, omissions, and delivery records

## Controls and permissions

A context package never grants access to its sources. Permissions are checked when material is assembled and used. A preview shows the test output; only a delivery record can establish what was supplied to an actual agent run.

## Example

A lithium compliance question needs a current bulletin, but it does not grant access to restricted review notes. Dynamic Context makes the included version and the permission omission visible in the preview, so the team can assess the package before using it with an agent.

## Workflow

### Test a specific request

- Ask about current telemetry and pending approval. Preview the context that this job-specific request would use.

### Inspect the included knowledge

- The preview includes the approved port bulletin and its source version. Review the material that supports the answer.

### Understand what is omitted

- Compliance review notes remain excluded when permission is denied. A context package does not bypass the access rules of its sources.

## Next steps

Start with the questions the agent must answer, the sources it may use, and the access boundaries the context must respect.

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