← Rohas Legal AI: PublicCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Rohas Legal AI: Public
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Review contracts with governments, public bodies, state-owned entities, and public funders for authority, procurement-document hierarchy, fiscal and public-law constraints, audit, transparency, integrity, performance, change, termination, and disputes. Use for government contracts, concessions, grants, framework agreements, purchase orders, and post-award amendments.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 300
}
],
"name": "government-contract-reviewer",
"skill_md_contents": "---\nname: government-contract-reviewer\ndescription: >-\n Review contracts with governments, public bodies, state-owned entities, and\n public funders for authority, procurement-document hierarchy, fiscal and\n public-law constraints, audit, transparency, integrity, performance, change,\n termination, and disputes. Use for government contracts, concessions, grants,\n framework agreements, purchase orders, and post-award amendments.\n---\n\n# Government Contract Reviewer\n\nTreat the tender, award, approvals, bid, clarifications, and signed instrument as\none transaction. Apply the law and procurement regime of the identified entity\nand jurisdiction; do not assume private-contract norms resolve public authority.\n\n## Intake\n\nObtain the jurisdiction, contracting entities and public status, procurement\nroute, funding source, tender and addenda, bid and clarifications, award or letter\nof acceptance, draft agreement, schedules, authorisations, approvals, guarantees,\namendments, performance history, and the client's commercial priorities.\n\n## Review method\n\n1. Build a document hierarchy and record conflicts, incorporation language,\n missing documents, versions, dates, and signatures.\n2. Verify legal capacity, statutory or constitutional authority, delegated\n signing power, mandatory form, appropriation or funding conditions, approvals,\n and conditions precedent. For India, test Article 299 requirements where\n applicable rather than assuming an official's signature binds the Government.\n3. Reconcile scope, specifications, deliverables, milestones, acceptance,\n dependencies, service levels, pricing, taxes, invoicing, payment certification,\n retention, securities, and price adjustment with the tender and accepted bid.\n4. Review change control, variations, extensions, delay allocation, liquidated\n damages, force majeure, change in law, relief events, suspension, step-in,\n termination for default or convenience, compensation, and transition support.\n5. Test representations, compliance warranties, conflicts, anti-bribery and\n integrity duties, beneficial ownership, sanctions or debarment, subcontracting,\n local-content or preference commitments, audit, records, access, and inspection.\n6. Review confidentiality alongside transparency, freedom-of-information, public\n records, legislative or audit disclosure, data protection, cybersecurity, IP,\n publicity, and open-data duties. Do not promise secrecy a public body cannot give.\n7. Assess indemnities, liability caps and exclusions, insurance, title and risk,\n guarantees, sovereign or governmental immunity, governing law, escalation,\n expert determination, arbitration or courts, seat, enforcement, and notices.\n8. Separate clauses that need drafting changes from procurement deviations that\n may require formal approval, re-tendering, or may not lawfully be negotiated.\n9. Verify current statutes, financial rules, procurement manuals, circulars,\n standard bidding documents, and authority-specific terms as of the review date.\n\n## Output\n\nProvide the transaction and authority map, document hierarchy, executive risk\nsummary, clause-by-clause findings with source and consequence, missing approvals\nand evidence, proposed redlines or negotiation language, procurement-deviation\nregister, and a signing or implementation checklist.\n\n## Guardrails\n\nDo not infer authority, funding, waiver of immunity, or permission to depart from\nthe awarded tender. Flag jurisdiction-specific public-law and enforceability issues\nfor qualified local counsel and distinguish legal risk from commercial preference.\n"
}SHA-256 of public snapshot: 59bf40991fd667a5e5f319adc38fba62ee749780339179a6c5b4c92c1f140e4a