Build Open Executive Intelligence Index framework

[murraylovecode]

Research identity

• Batch ID: BUILD-2026-08-14-001
• Protocol ID: protocol-BUILD-2026-08-14-001
• Prompt: OEII-MASTER-BUILD version 2.0
• Question: Which existing OFF conventions should the source-statement intelligence index reuse while preserving distinct canonical ownership?
• Source types: official public GitHub repositories and repository files

Batch results

• Accepted architecture sources: 6
• Rejected unrelated search results: 2
• Held: 0
• Production research records created or modified: 0
• Access basis: public read-only repository access at pinned commits

Required review

• Copyright and rights review recorded
• Privacy and confidentiality review recorded
• Duplicate review recorded
• Source-concentration review recorded
• AI assistance disclosed
• Independent automated checks recorded
• Named human methodology review
• Named human schema review
• Named human rights-policy review
• GitHub Actions browser tests
• Pages deployment and live verification

Human review status: pending. Publication recommendation: review the framework as a draft; do not publish research records or merge until the required owners approve.

Validation

npm run check passed. Type checking reported 0 diagnostics; 24 unit tests passed; 28 pages built; artifact checksums and fixture/staging exclusion passed. The local Playwright HTTP test passed and two process-launch tests were sandbox-skipped; the equivalent interactions passed in the in-app browser. GitHub Actions then passed all three hosted Playwright checks plus the schema/data, rights/privacy/content, unit, build, and artifact jobs. npm audit found 0 vulnerabilities. Deterministic build verification passed. Live verification was skipped because no deployment occurred.

Limitations

No production corpus or named human approval was supplied. The repository and this draft pull request are published, but the branch is intentionally unmerged and Pages/live verification remain pending. Repository-level write eligibility for @murraylovecode is verified; branch-protection and CODEOWNERS enforcement still require confirmation. See FINAL-IMPLEMENTATION-REPORT.md and the batch manifest for the complete record.