Acceptance checklists

Release verdicts

File 18 · Legal, Ethical, Privacy, and Safety Guardrails

Pre-release checklist

• □ Jurisdiction and channel are resolved.
• □ Source rights, robots, terms, and commercial-use status are current.
• □ Purpose and privacy basis are recorded.
• □ Collection is minimized and retention has an end state.
• □ No prohibited/sensitive enrichment enters prompts, embeddings, reports, or CRM.
• □ Contact provenance and outreach basis are independently verified.
• □ Message identity, postal/contact information, and unsubscribe controls pass.
• □ Suppression is checked at approval and again at send time.
• □ A human approves the exact message version.
• □ Correction, objection, deletion, and incident routes are operational.

Source: file 18 · 15-pre-release-checklist · line 309

File 20 · 360° Volumetric Intelligence Audit

5 Pre-send checklist

• □ Identity and role reverified on send date.
• □ Hook passes the evidence-use matrix and is role-relevant.
• □ Inferences/unknowns are explicit; no sensitive security/personal data.
• □ No guessed named email is used; contact provenance is lawful.
• □ Dollar figure is a labeled scenario or break-even.
• □ Sender identity, subject, contact/postal details, and disclosures are accurate.
• □ Jurisdiction, consent/lawful-use, suppression, and opt-out controls pass.
• □ Human approves the exact message.
• □ No message has been sent by this audit system.

Source: file 20 · 6-5-pre-send-checklist · line 403

File 20 · 360° Volumetric Intelligence Audit

3 CRM quality controls

• □ Email Pattern is a pattern, not a generated personal address.
• □ Unknown values are blank, not invented.
• □ Deal value is expected contract value, not modeled client loss.
• □ Company/role/contact provenance are current.
• □ Opt-outs and invalid contacts are suppressed.
• □ CSV formula injection is neutralized at export only.
• □ Currency, numeric, and date fields are typed.
• □ Organization/person/opportunity dedupe keys pass.
• □ A non-production sample import was reviewed.
• □ No CRM mutation occurred without explicit authorization.

Source: file 20 · 7-3-crm-quality-controls · line 438

File 21 · Quality Control and Acceptance Tests

Package integrity

• □ README.md exists and every referenced 00–21 file exists.
• □ Filenames sort in intended reading order.
• □ No unexpected binary, credential, token, cookie, cache, or personal-data file is included.
• □ Markdown headings are unique enough for navigation.
• □ Tables have consistent column counts and escaped literal pipes.
• □ Code fences are balanced and labeled where useful.
• □ Internal file references resolve.
• □ External links are syntactically valid and use official/primary sources where claimed.
• □ Research baseline and version appear in README.md.
• □ ZIP listing matches the expected manifest and excludes the ZIP itself.
• □ SHA-256 is generated for the final archive.

Source: file 21 · 2-package-integrity · line 14

File 21 · Quality Control and Acceptance Tests

Intake and scope

• □ Company legal/trade name and canonical domain are resolved or explicitly ambiguous.
• □ Executive identity, current role, and effective date are resolved separately from the company.
• □ Industry, geography, product scope, languages, and jurisdictions are declared.
• □ Offered services are specific enough to test mechanism fit.
• □ Audit as-of date, research window, comparison window, currency, and price year are declared.
• □ Engagement mode and expansion profile are declared and not confused with LAKA change states or architecture stages.
• □ Allowed, restricted, manual-only, and blocked source classes are recorded.
• □ Purpose, privacy, retention, outreach, and external-action boundaries are recorded.
• □ Up to three comparators pass a written comparison contract; fewer are used when comparability fails.

Source: file 21 · 3-intake-and-scope · line 40

File 21 · Quality Control and Acceptance Tests

Nine-phase completeness

• □ All seven report sections are present.
• □ Failed/blocked retrievals and research backlog are present.
• □ No phase is marked complete merely because a tool was run.

Source: file 21 · 4-nine-phase-completeness · line 54

File 21 · Quality Control and Acceptance Tests

LAKA coverage

• □ The 5×10 structural matrix has 50 completed or reasoned-N/A cells for Standard/Deep work.
• □ Critical findings have all fourteen dynamics completed or reasoned N/A.
• □ X-Standard/X-Deep work records the 140 variable–dynamic coverage status.
• □ Canonical 6×6×6 expansion records generated, deduplicated, eliminated, and promoted paths.
• □ X-Full, if used, is an offline 151,200-atom manifest—not 151,200 automatic searches.
• □ Coverage stops record saturation, duplication, budget, rights, risk, and evidence conditions.
• □ C0–C4 alternatives are not treated as maturity grades; C4 is not automatically preferred.
• □ The smallest useful reversible test is considered.
• □ Eliminated alternatives and re-entry triggers are preserved.

Source: file 21 · 5-laka-coverage · line 74

File 21 · Quality Control and Acceptance Tests

Evidence and provenance

• □ source ID, canonical URL/publisher, title/type, and exact passage or structured record;
• □ valid/event, publication, observation, and retrieval times kept distinct;
• □ access method, source-rights decision, terms/robots notes, and retention rule;
• □ content hash and archive/object locator where authorized;
• □ entity and scope match;
• □ E0–E5 level and O/C/I/H/U/X state;
• □ supporting, refuting, contextual, and common-origin relationships;
• □ strongest alternative and disconfirming check for high materiality;
• □ confidence components, not only a final label.

Source: file 21 · 6-evidence-and-provenance · line 88

File 21 · Quality Control and Acceptance Tests

Claim-type evidence use

• □ Official factual hooks are current E3+.
• □ Public-corpus calculations use E2+ source items from at least two independent origins with query, window, denominator, dedupe, sample limits, and reproducible calculation.
• □ Outreach corpus calculations receive human validation and privacy/defamation review.
• □ Inferences are adjacent to eligible facts/calculations and explicitly bounded.
• □ Hypotheses are falsifiable and include a diagnostic.
• □ Complaints/allegations remain experience reports; individual allegations never become outreach hooks.
• □ Security signals are excluded from sales outreach.
• □ Unknown/contradicted states are never factual hooks.

Source: file 21 · 7-claim-type-evidence-use · line 119

File 21 · Quality Control and Acceptance Tests

Technical and security safety

• □ Collection is CM0/CM1 only.
• □ CM2 activity is excluded and routed outside the system; CM3 is prohibited.
• □ No port/service probe, scan submission, exploit, authentication, credential test, breach dump, CAPTCHA/paywall bypass, deceptive account, or access-control circumvention occurred.
• □ Passive index data is time-bounded and not actively validated.
• □ Fingerprints do not become installed-version or vulnerability claims.
• □ MFA, patch, internal architecture, and exploitability remain unknown unless authorized evidence supports the exact claim.
• □ Security-sensitive findings are redacted and routed by responsible-disclosure policy.
• □ Secrets/credentials are never stored; only redacted type/location/time/fingerprint may be recorded.
• □ Untrusted documents are parsed in an isolated, patched, resource-limited environment.
• □ SSRF protections block loopback, private, link-local, metadata, and post-resolution rebinding targets.

Source: file 21 · 8-technical-and-security-safety · line 130

File 21 · Quality Control and Acceptance Tests

PR, sentiment, and narrative metrics

• □ Sampling universe, window, languages, geography, aliases, inclusion/exclusion, and platform bias are declared.
• □ SOV denominator is all entities in the comparison set: target plus selected comparators.
• □ Press-release syndication is one origin.
• □ Sentiment describes collected items, not customers or population opinion.
• □ Positive, neutral, negative, and uncertain are distinct.
• □ Model/rubric version, language coverage, human validation, denominator, and error are shown.
• □ Multi-label theme metric is called Issue prevalence in collected items; shares may exceed 100%.
• □ Crisis z-score is omitted when baseline standard deviation is zero.
• □ Review allegations are not adjudicated facts; response absence is scoped to the searched records.
• □ Corrective/misinformation claims require authoritative evidence and preserve legitimate criticism.

Source: file 21 · 10-pr-sentiment-and-narrative-metrics · line 158

File 21 · Quality Control and Acceptance Tests

Marketing and demand metrics

• □ “No ads found” is limited to the searched library/query/window.
• □ Public ad records do not become spend, conversion, reach, or profit claims.
• □ Rankings state date, location, language, device, and personalization limits.
• □ Trends/search-volume indices are proxies, not addressable demand or revenue.
• □ Content counts are deduplicated and use equivalent page/window definitions.
• □ Public tags do not prove correct analytics or attribution.
• □ GBP ratio is labeled actions per impression and may exceed 1.
• □ Field and lab performance data are not conflated.
• □ Automated accessibility findings do not claim complete conformance.

Source: file 21 · 11-marketing-and-demand-metrics · line 171

File 21 · Quality Control and Acceptance Tests

Competitor benchmark

• □ Comparison contract covers customer, job, offer, geography, model, scale, channel, and time.
• □ Up to three comparators are chosen for comparability; archetypes are optional labels, not quotas.
• □ Rejected candidates and mismatch reasons are preserved.
• □ Prices normalize unit, usage, term, setup, support, tax, currency/date, and promotion.
• □ Public feature and delivery claims remain claims unless measured.
• □ Unknown capability is not scored as failure.
• □ Fingerprint/job-post evidence does not prove production use.
• □ SOV uses the same corpus/query/window/dedupe for all entities.
• □ Competitive intelligence supports unilateral decisions only; no nonpublic price/output/strategy exchange or coordination.

Source: file 21 · 12-competitor-benchmark · line 183

File 21 · Quality Control and Acceptance Tests

Financial model tests

• □ result class and M0–M5 model class;
• □ every input tagged R/M/B/A, calculated result tagged C;
• □ currency, price year, nominal/real, period, horizon, and annualization;
• □ dimensional analysis reconciles;
• □ low/base/high or a defensible distribution;
• □ numeric range is monotonic (low ≤ base ≤ high) or the non-monotonic scenario labels are explicitly renamed;
• □ contribution margin versus revenue clearly distinguished;
• □ attribution, adoption, realization, lag, ramp, implementation, and ongoing cost;
• □ downside/zero case, sensitivity, switching value, and falsifier;
• □ overlap/dependency/mutual-exclusion group;
• □ formula/code/model version and frozen inputs;
• □ not estimable — missing inputs when appropriate.

Source: file 21 · 13-financial-model-tests · line 195

File 21 · Quality Control and Acceptance Tests

Outreach authority and compliance

• □ Recipient identity/role/remit are current and exact enough.
• □ Hook passes the claim-type evidence-use matrix.
• □ Business relevance is direct; no psychological profiling or private-life detail.
• □ Intrusiveness ≤1, unsupported certainty ≤1, respectful boundary ≥4, AuthorityScore ≥18.
• □ Security, credential, vulnerability, protected-trait, family, health, and personal-distress material is excluded.
• □ Scenario/break-even is labeled and target-private knowledge is disclaimed.
• □ Subject line is truthful and not fear/deception/fake reply.
• □ CTA is permission-based and useful.
• □ Jurisdiction and channel legal pack passes.
• □ Contact source/status and consent/lawful-basis evidence are current.
• □ Sender identity/contact/postal details and unsubscribe/objection controls pass.
• □ Suppression is checked at approval and send time.
• □ Human approves the exact message; the audit system does not send.

Source: file 21 · 14-outreach-authority-and-compliance · line 225

File 21 · Quality Control and Acceptance Tests

CRM and export

• □ Required headers exactly match the requested 11 columns.
• □ Governance view retains entity, evidence, claim, model, jurisdiction, contact, suppression, review, and retention fields.
• □ Email Pattern is an organization pattern or blank; never a materialized guessed mailbox.
• □ Published, verified, pattern-only, unknown, invalid, opted-out, and suppressed remain distinct.
• □ MX presence is not mailbox verification or permission.
• □ Estimated Deal Value is expected contract value, not client loss or value delivered.
• □ Blank is preferred to invented data.
• □ Canonical values remain unchanged; spreadsheet neutralization occurs at export.
• □ Strings beginning after whitespace/control characters with =, +, -, @, tab, CR, or LF are neutralized for spreadsheet use.
• □ Quotes, commas, CR/LF, NUL, Unicode controls, dates, currency, and numbers pass typed tests.
• □ API upserts/deletes are idempotent and retain remote receipts.
• □ CRM remains a projection, never evidence/identity master.

Source: file 21 · 15-crm-and-export · line 241

File 21 · Quality Control and Acceptance Tests

Privacy, retention, and deletion

• □ Every personal record has purpose, jurisdiction, owner, and review/delete time.
• □ Data is minimized before prompts, embeddings, reports, and exports.
• □ Sensitive/protected/minor/private-family data is absent or explicitly blocked.
• □ Processing restriction applies before physical deletion completes.
• □ Deletion enumerates canonical DB, objects/versions, OCR, summaries, embeddings, search, graphs, analytics, reports, exports, CRM, caches, and backups.
• □ Every target returns a receipt or documented expiry/exception.
• □ privacygeneration blocks delayed-event resurrection.
• □ Projection rebuild and old-backup restore replay the deletion ledger.
• □ Suppression survives deletion with only an authorized non-sensitive keyed token.
• □ Cross-tenant reads, vectors, reports, exports, and connector jobs fail closed.

Source: file 21 · 16-privacy-retention-and-deletion · line 270

File 21 · Quality Control and Acceptance Tests

Tool-registry acceptance

• □ official source/docs and verified date;
• □ software license separated from upstream-content permission;
• □ deployment/free-tier/commercial-use classification;
• □ authentication, quota, and rate behavior;
• □ allowed/prohibited data and methods;
• □ CM and LAKA impact classification;
• □ provenance input/output schema;
• □ retention/deletion and tenant-isolation behavior;
• □ owner, review date, kill switch, and terms-change trigger.

Source: file 21 · 17-tool-registry-acceptance · line 283