S186 Correction — User Approval Role and Next Pilot Direction

Date: 2026-04-29

Correction from User

User clarified that they do not want to approve technical evidence they cannot inspect. GPT is responsible for technical/law/constitutional supervision. User wants to see the final outcome: whether information units have been created from real documents and can be viewed/assembled.

Correct interpretation

P9/G8 completion means the foundation is ready:

• PostgreSQL schema exists.
• Directus collections exist.
• Vocab/config seed exists.
• Roles/permissions/tokens exist.

But the actual information-unit corpus is not yet migrated:

• Core/member tables remain 0 rows.
• No real documents have been split into TAC units in production yet.
• No user-visible assembled document view exists yet.

Therefore, User-facing acceptance should not be framed as asking User to approve technical deployment internals. GPT can accept/approve technical foundation. User should review visible outcome after a small pilot.

New direction

After GPT technical closeout of P9 foundation, next step should be a small separately gated pilot:

P10 / Pilot Cut-and-Render Gate

Goal:

• Select a few real documents.
• Segment them into information units.
• Insert into TAC core/member tables through governed process.
• Assemble them back by document/file pivot.
• Provide a view or evidence that User can inspect.

This is where User can evaluate whether “miếng thông tin đã lên được chưa”.

Directive change

Do not ask User to approve technical internals as if User is expected to audit SQL/Directus/GSM. Instead:

1. GPT confirms technical foundation according to law/constitution.
2. Opus drafts closeout as GPT technical acceptance / foundation ready.
3. Opus then drafts the next pilot plan/prompt for cutting a few documents and rendering them back as documents.
4. User reviews the visible pilot result.

Important guardrail

The pilot is a new gate. It is not automatically authorized by P9. It must have its own design/review, because it will insert real TAC core/member records and possibly create a Nuxt/Pivot rendering surface.