Final Submission Video ExecPlan

This public sanitized ExecPlan closes the remaining local work for the AITrailblazer AI Agent Publishing submission. It does not include private operator evidence, credentials, account metadata, or unreleased claims.

Task

Finish The Final Devpost Gate

Prepare the under-three-minute demo video workflow and make the public repo, hosted demo, README, submission pack, and readiness automation point judges to the exact final path. The only intentionally external remaining action is recording/uploading the video and pasting its public URL into Devpost.

Allowed Changes
  • Root public HTML artifacts.
  • README, changelog, and consolidated public docs.
  • Static serving allowlist, Dockerfile, Makefile, tests, and readiness scripts.
  • Video URL validation helper that accepts only public URLs supplied by environment variable.
Forbidden Changes
  • No credentials, cookies, account metadata, billing exports, or private screenshots.
  • No claims that this submission is a live SEC/XBRL market-data product.
  • No investment recommendations, paid-route pricing claims, or trading signals.
  • No additional files under docs/; the docs folder remains one canonical HTML artifact.
Implementation Steps
  1. Create this public sanitized ExecPlan as a root HTML artifact.
  2. Add a final video URL checker script and Makefile target.
  3. Link this ExecPlan from the hosted root, README, Devpost submission pack, and consolidated docs.
  4. Update readiness automation to verify the hosted ExecPlan and the public repository copy.
  5. Keep the final video URL as an explicit manual Devpost gate until a public YouTube or Vimeo URL exists.
  6. Run local tests, public scans, hosted deployment, and final submission readiness.
Three-Minute Video Runbook
  1. 0:00-0:20 Problem: expert publishers have years of articles, but readers cannot reuse claims, updates, or follow-up context through normal archive search.
  2. 0:20-0:45 Solution: AITrailblazer turns a publication archive into MongoDB-backed agent memory using Trip Codes, River links, claims, sessions, MongoDB MCP, Gemini, Agent Builder, and Cloud Run.
  3. 0:45-1:25 Live Trip Code demo: enter HUT-RIVER-001 and show resolved article, three River articles, claim cluster, River edges, and source context.
  4. 1:25-1:55 Runtime proof: show Gemini live, Agent Builder live, MongoDB live, MongoDB MCP live, and Cloud Run hosted proof.
  5. 1:55-2:25 Follow-up memory: ask What should I monitor next? and show the agent continuing from reader-session memory.
  6. 2:25-2:50 Impact: explain how this generalizes to newsletters, research firms, technical blogs, local journalism, financial research, and any publisher with a valuable archive.
  7. 2:50-3:00 Close: MongoDB is the memory layer, MCP is the agent access path, Gemini is the synthesis layer, and Cloud Run is the live runtime.
Acceptance Criteria
Remaining Manual Gate

Record and upload the final under-three-minute public demo video, then paste the URL into Devpost. Do not click final Devpost submit without explicit human confirmation.