liveBook · Manning

Context package

As explained in Architecting for Autonomy

A curated structured bundle of evidence, instructions, authorities, policy results, and other contextual material supplied to an agent or model for a particular purpose.

A context package is a structured bundle of material assembled for an agent’s particular purpose. In a contract dispute, it might bring together delivery records, correspondence, contractual clauses, legal authorities, and policy results for a supervised assessment. Access to an item alone does not authorize every use of it: reading an email is different from placing it in model context, quoting it externally, or using it to support a legal position. section 5.1.1 section 5.2.1

A governed package pairs the context payload with a Trusted Context manifest. The payload holds the material supplied to the agent; the manifest records the conditions for its use, including the matter, purpose, decision surface, authority ceiling, evidential status, exclusions, policy basis, expiry, and rebuild triggers. The manifest preserves distinctions between verified records, disputed statements, generated interpretations, and applicable authorities; it does not turn uncertain material into fact. section 5.2.1

At the context-assembly boundary:

  • Qualify each item for the proposed use and authority level. A preliminary evidence-organizing task can tolerate more uncertainty than a settlement recommendation or formal response. section 5.2.1
  • Admit, qualify, restrict, exclude, or transfer candidate material using its metadata, evidence status, policy state, proposed use, and authority ceiling. Bind the versioned manifest to the payload and propagate conditions into later uses. section 5.8.3
  • Preserve conflicting evidence, unresolved uncertainty, deliberate exclusions, and lineage from derived artifacts to their evidence. Record material transformations without requiring exposure of hidden model reasoning. section 5.1.1 section 5.2.1

Supervised dispute assessment

For a preliminary breach assessment, verified delivery records and order-volume history can be distinguished from partly disputed correspondence, an unverified call transcript, and an agent-generated chronology. The chronology helps navigation but does not acquire the evidential standing of its source records. The authority ceiling limits the result to a draft for supervising-lawyer review. section 5.2.1

Listing 5.1 Sample Trusted Context Manifest
Context ID: TC-MATTER-1042-07
Matter: Retailer v. Logistics Supplier
Purpose: Prepare a supervised preliminary position on contractual breach
Decision surface: Internal breach and damages assessment
Authority ceiling: Draft for supervising-lawyer review
 
Applicable legal and contractual frame:
Commercial Supply Agreement, version 3 
Amendment 2, effective 1 October 
Service-Level Schedule, version 4 
Governing law: England and Wales 
Judicial authorities verified for jurisdiction, currency, and proposition
 
Admitted material:
Delivery records for the disputed period: verified operational evidence 
Order-volume history: verified business record 
Supplier correspondence: authenticated, content partly disputed 
Supplier-call transcript segment: derived representation, unverified 
Agent-generated chronology: interpretation, not source evidence
 
Excluded material:
Superseded version of Clause 7 
Documents belonging to other matters 
Privileged correspondence not permitted for the current drafting purpose 
Authorities from an inapplicable jurisdiction 
Transcript segment below the approved confidence threshold
 
Permitted use: Internal research, chronology, issue identification, and supervised drafting
Prohibited use: External disclosure, formal admission, autonomous settlement recommendation, or persistent cross-matter memory
Policy basis: Matter isolation, privilege, evidence threshold, citation, and professional-review policies
Expiry: End of the current review session or material change to the matter
Invalidation triggers: New amendment, corrected evidence, changed permission, conflicting authority, policy update, or request for a higher-authority action
Required reviewer: Supervising lawyer

Inspect a sample manifest that binds a dispute assessment to its purpose, authority ceiling, applicable frame, and admitted material. section 5.2.1

How Architecting for Autonomy covers it

How deep it goes
Specifies payload and manifest fields, admission outcomes, binding, and propagation, without detailing a particular implementation.
Examples
Uses a contract dispute with delivery records, disputed correspondence, an unverified transcript, and a generated chronology.
What you can do after
Operate/configure a context admission boundary that applies manifest conditions and carries restrictions into subsequent uses.
How it connects
Connects delegated authority with evidence quality, data lineage, policy enforcement, and disclosure boundaries.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting for Autonomy. The section links point to the parts of the book it draws on.