Skip to content

docs: consolidate portfolio authority and verification - #36

Draft
atomicdjt wants to merge 1 commit into
mainfrom
portfolio/governance-cleanup-2026-07-19
Draft

docs: consolidate portfolio authority and verification#36
atomicdjt wants to merge 1 commit into
mainfrom
portfolio/governance-cleanup-2026-07-19

Conversation

@atomicdjt

Copy link
Copy Markdown
Owner

Purpose

Replace the noisy remediation branch with one clean, reviewable governance patch based directly on main.

Changes

  • keep config/vercel-projects.json as the single canonical project/deployment catalog;
  • correct WeaveStudio authority to main and retain BuildWorld’s unresolved production-target boundary;
  • synchronize the root README, recruiter guide, employer overview, project index, rankings, and verification guide;
  • add one portfolio-authority validator and run it from the existing Portfolio CI workflow;
  • document AI-assisted authorship and evidence boundaries;
  • add an ethical external-validation protocol;
  • add change-control and Vercel-consolidation runbooks;
  • preserve the existing guarded affected-project deployment controller and explicitly defer native-Git cutover until credentials, a single-project preview, and rollback are verified.

Safety boundary

  • one commit based directly on main;
  • no application source changes;
  • no production branch changes;
  • no Vercel project, domain, alias, environment variable, or deployment deleted or modified;
  • no unsupported traction, customer, revenue, security, or production-readiness claims;
  • no automatic merge.

Pre-publication validation

  • authority validator passed against the assembled tree;
  • JSON and workflow YAML parsed successfully;
  • changed-document link targets were checked against the patch and existing repository paths;
  • the exact Git commit was compared with main: 14 files, one commit, zero app-source changes.

Required before merge

  • Portfolio CI must complete successfully, including documentation, authority, deployment-policy, selector, lint, typecheck, tests, and builds;
  • Vercel checks must no longer be failing for an unresolved rate-limit or build reason;
  • review the wording and canonical URLs;
  • leave account-level Vercel cleanup for an explicitly approved, separately verified operation.

@vercel

vercel Bot commented Jul 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ai-project-portfolio-opspilot-ai-operations-toolkit Ready Ready Preview, Comment Jul 19, 2026 9:58pm
ai-project-portfolio-scamshield-ai Ready Ready Preview, Comment Jul 19, 2026 9:58pm

@vercel

vercel Bot commented Jul 19, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/atomicdjts-projects?upgradeToPro=build-rate-limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant