GPT Review — Registries-Pivot Final Route External Check Failed

Date: 2026-05-31 Reviewer: GPT Council

Finding

Agent reported PASS for production route /knowledge/registries-pivot, but GPT external web check returned the generic Knowledge document renderer with Document not found, not the interactive Registries-Pivot UI.

Observed URL: https://vps.incomexsaigoncorp.vn/knowledge/registries-pivot

Observed content:

• Incomex AI Portal generic knowledge shell;
• Browse Contents;
• Document not found.

Therefore, the final acceptance condition is not met from an external/user perspective.

Compliance notes

The intended implementation can comply with the laws only if:

• Nuxt is render-shell only;
• no frontend count logic;
• no hardcoded counts/categories/species/layers/labels/pins/thresholds;
• all counts come from PG/pivot-backed views or PIVOT_MISSING;
• rollback exists.

However, the agent-reported direct read-only PG API path is not the ideal final PG→Directus/API→Nuxt convention. If kept, it must be explicitly approved as an API exception, or Directus view exposure must be fixed.

Required next action

Run a strict external-user verification and repair mission. PASS is forbidden unless an external curl/browser check to /knowledge/registries-pivot shows the interactive dark registry table, not the generic document renderer.

The agent must check possible causes:

• route file exists but production Nuxt container not rebuilt/restarted;
• route shadowed by /knowledge/[slug] generic catch-all;
• nginx/cached build serving old .output;
• route order issue;
• Nitro build artifact missing;
• deployment went to wrong directory/container.

Decision

Current status from GPT: PARTIAL, not PASS.