NYC Local Law 144 · for Legal evidence workflow

NYC Local Law 144 evidence for legal AI workflows.

Open the Console Open the Law brief

For general counsel and litigation support: use the self-serve API to gate the workflow and link the NYC Local Law 144 requirement to the evidence record for the legal AI workflow under review.

FRE 702 · ABA Model Rules
01 ·

What you get.

Three things a law program office gets when NYC Local Law 144 lands in the record.
Named control

NYC Local Law 144 in ATTESTATION.json

Every artifact your legal AI workflow emits is hashed and named; the NYC Local Law 144 control reference sits next to the hash.

Sector framing

Law anchors named alongside

The evidence record names FRE 702 · ABA Model Rules together. Internal or external law compliance sees the regime they care about, not a generic list.

Reproducible

Bit-exact on your hardware

The measurement engine runs in-enclave. Law evidence rules can permit recompute on customer infrastructure; the record supports that review property by construction.

02 ·

Related coverage.

Other Planisphere surfaces for this combination.

NYC Local Law 144 reference · Open the NYC Local Law 144 reference · NYC Local Law 144 capability brief · Law vertical landing

Every law-shaped landing for the corpus lives under register 09.

See the Legal evidence workflow path in the Console.

Open the Console to see sealed records; the Docs carry the endpoints.

Open the Console NYC Local Law 144 reference Law vertical
API ·

When NYC Local Law 144 asks for proof, hand over records — not assurances.

record the duty · seal the receipt · verify offline

Planisphere records each duty event — an output marked, a disclosure shown, a review made — and seals it into a receipt that verifies offline against our published keys. You send hashes, never content. A record is evidence a third party can check; it is not a certification and not a legal determination.

Open the Console Read the Docs Read the capability briefing

See how a record is checked