DPO Radio

Legal Counsel Persona

Overview Image

Why the Legal Counsel Persona Matters

A legal counsel reviewing a vendor DPA needs three things at once. They are the GDPR Article 28 controller-processor clauses to map against, the organisation's clause library to compare for negotiated language, and a rejection record for every suggested redline that was not accepted. A general-purpose AI assistant cannot deliver any of the three; it answers with plausible-sounding language drawn from training data, with no defensible record afterwards.

The Forseti Legal Counsel persona is tuned for the contract review motion. It comes with no regulatory pack of its own: each conversation is grounded in the frameworks your organisation has installed, and it reads your contracts and other documents through its document search and read tools, within the permissions of the person asking. Its tool affinity is biased toward document search, document read, the redline document review surface, and the contract-lane workflows (vendor DPA GDPR Article 28 review, contract obligation extraction, contract redline assistant). Every suggestion ships with an inline citation to the framework requirement and the clause library entry it draws from.

The Legal Counsel does not act autonomously. Forseti drafts redlines; the legal counsel accepts or rejects each one. The version history is immutable. Rejections persist with operator and time. When an auditor or a partner asks why a clause suggestion was not accepted, the record is in the version history.

How It Works

Grounded in Your Installed Frameworks and Documents

The Legal Counsel persona pre-loads no regulatory pack and no contract corpus. Each conversation tells it which frameworks your organisation has installed, and it may cite a framework only when its regulatory search returned that text in the same turn. Contracts are read on demand through document search and document read. Where your organisation has installed, say, GDPR and DORA, cross-framework contract reasoning (GDPR Article 28 beside DORA Article 28 for the ICT third-party register) stays in one conversation.

Tool Affinity for Contract Work

The persona reaches for document search, document read, the redline document review surface, and the contract-lane workflow pack first. Tabular reviews (N × M comparison across vendor contracts) sit one click away.

Clause-Library Lookup With Citation

Every clause suggestion ships with a citation back to the clause library entry and to the framework requirement the clause supports. Suggestions without grounding are flagged with a "no grounding" marker rather than fabricated authority.

Jurisdiction-Aware Risk Language

Suggestions are pinned to the relevant jurisdiction — Vietnamese contract law, English contract law, EU contract law — based on the contract's governing law clause. The risk language adapts to the jurisdiction.

Vendor DPA GDPR Article 28 Review Workflow

A one-click workflow that walks a vendor DPA against the GDPR Article 28 requirements (controller-processor clauses, sub-processor obligations, audit rights, breach notification, return-or-destruction). The output is a clause-by-clause analysis with citations and a follow-up task list.

Off-Topic Refusal

A question about ISO 27001 control coverage or vendor risk acceptance triggers a redirect to the Compliance Specialist or Risk Analyst persona. A question outside the legal scope entirely triggers the standard off-topic refusal block.

The Difference

Graphic Image

Without a Legal Counsel Persona

Graphic Image

With the Forseti Legal Counsel Persona

IconContract reviews happen against a general-purpose AI that cannot ground suggestions in the organisation's clause library.
IconThe persona works over the frameworks your organisation has installed and reads contracts on demand.
IconRejection records for redline suggestions either do not exist or are kept in side-channel comments.
IconEvery clause suggestion ships with a citation to the framework requirement.
IconJurisdiction-aware risk language is reconstructed from memory each time.
IconJurisdiction-aware risk language adapts to the contract's governing law.
IconThe vendor DPA review motion is bespoke per counsel, with no standard structure.
IconThe vendor DPA GDPR Article 28 review is a one-click workflow with structured output.

Built for Auditable AI

Build For Image

Every clause suggestion ships with an inline citation. The redline document review surface preserves immutable version history; rejections persist with operator and time. The audit story for an unaccepted suggestion is in the version history.

Build For Image

No clause suggestion auto-applies. The legal counsel accepts each suggestion. The version history records both accepted edits and rejected suggestions.

Build For Image

The persona prompt is reviewable on request. It ships in the runtime persona pack and is identical on every tier — no tier offers a tenant-level override, so the counsel's citation discipline and refusal block cannot be edited away.

Overview Image

From Agreement Review to a Proposed Change

Use the processor agreement playbook in English or Vietnamese to review terms against installed requirements. For your own negotiation positions, open Contract Playbooks. Use Verifying Quotes and Drafts to inspect the exact words behind a finding.

Background Image

See the Legal Counsel Persona in Action

Ready to see a vendor DPA walked against GDPR Article 28 in five minutes with citation per clause and a clean rejection record? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Pilot the Legal Counsel persona against your active contract pipeline. Run the vendor DPA GDPR Article 28 review workflow and measure how the rejection record holds up against your firm's audit standard.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how to tune the clause library and the jurisdiction set for your contract portfolio.

Frequently Asked Questions About the Legal Counsel Persona

Contract review, DPA analysis, vendor agreement walkthrough, clause-library comparison, jurisdiction-aware redline suggestions, and the vendor DPA GDPR Article 28 review workflow. The persona's tool affinity is biased toward document search, document read, and the redline document review surface.

No. The legal counsel accepts or rejects each redline. The version history is immutable; both accepted edits and rejected suggestions persist with operator and time.

Suggestions are pinned to the relevant jurisdiction based on the contract's governing law clause. Vietnamese, English, and EU contract-law conventions adapt the risk-language wording. The framework citations come from the frameworks your organisation has installed and apply identically regardless of jurisdiction.

Yes. The persona's tool affinity includes the tabular review surface. The legal counsel runs an N × M comparison across the vendor agreement portfolio — governing law, dispute resolution, liability cap, indemnity, termination notice, IP assignment — with citations per cell.

The suggestion ships with a "no grounding" marker rather than fabricated authority. The legal counsel sees the marker and can reject the suggestion or request a grounded alternative. This is part of the citation-grounding contract — no grounding, no conclusion.