← Rohas Legal AI: PublicCONTENT HISTORY

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.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Check a public or private tender, RFP, RFQ, auction, or bid for eligibility, responsiveness, technical and commercial evidence, forms, securities, portal mechanics, and deadlines. Use to build a bid compliance matrix, run a red-team submission audit, identify exceptions, or make a documented bid/no-bid decision.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 263
    }
  ],
  "name": "tender-compliance-checker",
  "skill_md_contents": "---\nname: tender-compliance-checker\ndescription: >-\n  Check a public or private tender, RFP, RFQ, auction, or bid for eligibility,\n  responsiveness, technical and commercial evidence, forms, securities, portal\n  mechanics, and deadlines. Use to build a bid compliance matrix, run a red-team\n  submission audit, identify exceptions, or make a documented bid/no-bid decision.\n---\n\n# Tender Compliance Checker\n\nTreat the issued tender, schedules, standard terms, corrigenda, clarifications,\nportal instructions, and incorporated policies as one controlled document set.\nNever assume a missing form or deviation can be cured after the deadline.\n\n## Intake\n\nObtain the complete tender package, all addenda and pre-bid answers, procurement\nportal record, authority and jurisdiction, bid structure, bidder and affiliates,\nconsortium or subcontractors, credentials, technical solution, pricing, securities,\nsubmission deadline and timezone, and internal owners and approvals.\n\n## Checking method\n\n1. Create a document register with issue dates, versions, hierarchy, addenda,\n   incorporated documents, conflicts, and bidder acknowledgements.\n2. Extract every requirement into a traceable matrix: source and clause, exact\n   requirement, mandatory or evaluative status, pass condition, evidence, form,\n   owner, dependency, due date, response location, and review status.\n3. Test eligibility and exclusion criteria, registrations, licences, experience,\n   turnover and net worth, similar contracts, conflicts, litigation disclosures,\n   debarment, sanctions, beneficial ownership, integrity, tax and labour compliance.\n4. Check consortium, joint-venture, affiliate, OEM, key-personnel, subcontractor,\n   local-presence, local-content, MSE, startup, preference, and reciprocity rules\n   against the exact definitions and evidence requirements.\n5. Reconcile specifications, scope, deviations, deliverables, methods, staffing,\n   milestones, service levels, acceptance, warranties, implementation, and proofs.\n6. Audit pricing schedules and BOQ for currency, taxes, arithmetic, units, discounts,\n   escalation, omissions, conditional pricing, signatures, locks, and consistency\n   with the technical offer without altering protected source workbooks casually.\n7. Verify bid security or declaration, performance security commitments, powers of\n   attorney, board approvals, declarations, notarisation, apostille, signatures,\n   digital certificates, file formats, size limits, naming, encryption, and sealing.\n8. Rehearse portal submission, access, uploads, signatures, payment, final submit,\n   receipt capture, deadline and timezone. Keep a fallback and escalation plan.\n9. For India public procurement, verify the latest applicable GFR compilation,\n   goods, works, consultancy or non-consultancy manual, GeM or portal rules,\n   preference orders, restrictions, vigilance guidance, and procuring-entity terms.\n10. Separate curable gaps, material deviations, clarification questions, approval-\n    dependent exceptions, and absolute blockers. Recheck every addendum before filing.\n\n## Output\n\nProvide the document register, compliance matrix, eligibility and evidence table,\ndeviation and clarification log, technical and commercial cross-check, submission\nchecklist, blocker report, owners and deadlines, and a reasoned bid/no-bid status.\n\n## Guardrails\n\nDo not mark compliance from narrative assurance alone, conceal a deviation, invent\ncredentials or certificates, or rely on a hoped-for post-bid cure. Preserve the\nissued files and submission receipt, and escalate ambiguous mandatory conditions\nbefore the clarification or bid deadline.\n"
}

SHA-256 of public snapshot: f44ce34c418d0494a1db06a2664118ef94078164f4279e34825c8e3a94953dbe