Jus 9 Tecnologia Juridica - OpenAI Build Week 2026 reviewer path

Work and Productivity

Jus 9 DAJ

A governed legal-intake and case workflow that preserves a reviewable record from fictional intake to AI-assisted analysis, human routing, official public metadata, and one-DAJ-to-one-case linkage.

ProductPublic workflow live
Build evidenceGit, CI, and repository hygiene verified
EligibilityOfficial clarification pending

Live governance API

Inspect what Charlie may do — and what remains blocked

A public, read-only and minimized endpoint exposes the active G6C2 permission boundaries, confirmation gates, DataJud read-only status, PDPJ readiness-only status, blocked judicial effects, and the unanswered CNJ institutional channel. It grants no permission and contains no credentials or personal data.

MVP consolidation

One operational pilot, thirteen governed showcases

The current Mao na Massa direction is to keep DAJ as the operational Build Week pilot, keep the other MVPs as public governed showcases, and move shared behavior into a versioned Charlie Core.

ScopeStateReviewer note
DAJ pilotActive pilotFictional intake, DAJ registry, mandatory laudo analysis, review routing, and read-only public metadata.
13 MVP expansionsGoverned demosPublic showcase pages use fictional datasets and explicit human-review limits.
Charlie Core 1.2.0ImplementedShared policies, MVP registry, risk classification, governed response contracts, provenance, limits, human review, and minimized audit are covered by automated tests.
Drive and memoryControlled review onlyDAJ reversibility closed with corrective caveats. Drive and memory may use only fictional data in authorized, reversible homologation; production and real data remain blocked.
Judge packagePrivate ZIP preparedThe credentialed package is delivered privately, scanned, hashed, and kept outside the public repository. The video script is a separate owner artifact.

Judge test

Verify the core flow in three minutes

Credentials are supplied only in the private judge package. Use fictional data throughout the review.

  1. 01

    Create a fictional DAJ

    Persist a synthetic intake and retain the generated DAJ identifier.

    Open intake
  2. 02

    Inspect the governed laudo

    Open the isolated Charlie room and verify facts, gaps, limits, feedback, and human routing.

    Open Charlie
  3. 03

    Verify the official-source boundary

    Check read-only CNJ-number metadata or the declared fail-closed state. No generative substitute is allowed.

    Open processes

Live product

Review the working path in order

The public tour exposes the real interface. Write operations require a least-privilege judge session and synthetic data only.

  1. 01

    Create a fictional legal intake

    Capture the case summary, classify urgency and secrecy, then persist the official DAJ record through the governed backend.

    Open intake
  2. 02

    Request analysis in an isolated room

    Charlie Echo receives a minimized DAJ context and must return a structured laudo with facts, missing information, explicit limits, feedback, and human routing.

    Open Charlie Echo
  3. 03

    Query official public metadata

    CNJ case-number search uses the read-only DataJud connector. Unsupported party searches fail closed and never receive generated substitutes.

    Open processes
  4. 04

    Link and route the work

    One DAJ maps to one case while a person can have several DAJs. Team roles govern the next human review and preserve accountability.

    Open team roles

Significant extension

What changed during Build Week

The repository existed before the event. Evaluation is explicitly limited to work added after July 13, 2026 at 9:00 AM Pacific Time.

Product work

  • Backend-persisted and idempotent DAJ intake
  • Isolated DAJ analysis with mandatory laudo, feedback, and human routing
  • Read-only DataJud client, cache, normalization, readiness, and audit controls
  • One-DAJ-to-one-case linkage with privacy-minimized party indexing
  • Per-user memory, governed Drive operations, and fail-closed response contracts

Reproducible proof

Baseline commit: a45ae2c. The audit reads Git directly, checks the public reviewer path, and rejects unsupported claims in strict mode.

node scripts/audit-build-week-readiness.mjs
node scripts/audit-build-week-readiness.mjs --strict
Open the baseline comparison

Codex Sol evidence

Activated: July 13, 2026 at 6:37:59 PM BRT. First active turn: 6:40:30 PM. First code edit: 6:53:47 PM.

Elapsed since verified Codex activation Live calendar time since the verified gpt-5.6-sol activation, not accumulated compute time. Charlie Echo's production runtime remains unverified.

Evidence seal: d2cfd341b2ad8c4e95e47977f4a90bd3b023cde50977efd345d08d51904a54b9

The full task identifier is retained privately. This verifies gpt-5.6-sol for Codex development only; it does not attest the Charlie Echo production runtime.

OpenAI production toolchain: the founder confirms that the ecosystem's production work through July 21, 2026 was constructed exclusively with ChatGPT, Codex, and the OpenAI API, under human authorship and review. This does not claim sponsorship, formal partnership, or OpenAI authorship of Cloudflare, GitHub, Google, CNJ sources, libraries, standards, or other third-party infrastructure.

The public Jus 9 Carta records the broader contribution of OpenAI tools to writing, memory, documentation, repositories, governance, and technical construction.

Pacote 8 closeout

Final delivery status

The private judge package has been authorized for freeze and is delivered outside the public repository. Eligibility, asset rights, video recording, and final submission remain human decisions.

GateStateRequired human action
General reviewREVISAO_GERAL_EXECUTADAKeep the review record and audit output attached to the final package.
Repository hygieneCleanThe 26-file legacy ZIP audit extraction was removed from Git. Temporary folders and archive formats remain denied by repository policy.
EligibilityClarification pendingObtain written confirmation before submitting as a Brazil resident.
Judge accessReady privatelyA founder-confirmed Google login is included only in the private judge package; use synthetic data only.
Asset rightsOwner signoff pendingComplete the declaration before using screenshots, marks, cards, or narration.
Demo videoScript readyHuman recording remains pending. Keep it under three minutes and do not expose credentials, CPFs, real process records, or private Drive files.
Private judge ZIPPrepared and hashedCredentialed delivery is separate from the repository and excludes AI handoff notes and the video script.

Truthful by construction

Verified claims and explicit limits

Technical availability is not presented as legal authorization, and an unavailable official source never becomes a generated answer.

ClaimStateReviewer note
Codex collaborationVerifiedTimestamped development record and Git evidence
Codex development modelVerifiedgpt-5.6-sol active from July 13, 2026 at 6:37:59 PM BRT; sanitized evidence only
OpenAI API integrationVerified in sourceRuntime model is selected by deployment configuration
OpenAI production toolchainFounder confirmedChatGPT, Codex, and the OpenAI API were the exclusive AI production tools through July 21, 2026; third-party infrastructure remains separately attributed.
Charlie Echo GPT-5.6 runtimeUnverifiedDevelopment evidence is not a production-runtime attestation
Brazil entrant eligibilityClarification pendingCurrent rules appear to exclude Brazilian residents
DataJudRead-onlyPublic metadata by CNJ number; no case files or transactional acts
Charlie governance APILive, read-onlyDefault-deny capability state is inspectable without credentials; it executes no effect
CNJ institutional channelAwaiting responseFollow-up check is scheduled for July 22 at 10:00 AM BRT; silence grants no authorization
External name or CPF searchUnavailableThe product fails closed while official guidance and credentials are pending

System design

One workflow, governed components

PortalIntake, DAJ, processes, team
Worker gatewayAuthentication, policy, audit
Charlie Echo APIIntent, governed context, OpenAI
Official connectorsDrive and read-only DataJud

Source review

Inspect the evidence without guessing

The README distinguishes the pre-existing platform from Build Week work, records related repositories, and names every unresolved dependency.