LAKA Volumetric Intelligence System

This library turns public company intelligence into evidence-backed commercial insight and respectful executive outreach. It combines passive OSINT, PR and brand intelligence, marketing-demand analysis, micro- and macroeconomics, competitor benchmarking, financial scenario modeling, and CRM-ready lead records.

It is a grammar and operating system, not a single giant prompt. Every output must preserve the chain:

source → observation → claim state → confidence → mechanism → financial range → service fit → smallest useful next step

What makes it volumetric

The system combines four LAKA layers:

1. Five change states: Baseline, Minor Change, Major Change, Structural Change, Paradigm Change.
2. Ten internal variables: Object, Conditions, Actions, Tools, Resources, Outcomes, Feedback, Constraints, Value, Failure Mode.
3. Fourteen change variables: Magnitude, Rate, Direction, Scope, Depth, Duration, Frequency, Acceleration, Variability, Detectability, Reversibility, Propagation, Amplification, Accumulation.
4. A 6×6×6 expansion lens: Who/What/When/Where/Why/How × Direction/Scope/Depth/Duration/Frequency/Reversibility × six execution-impact states.

The result is broad coverage without pretending that every possible web page, tool, or future data source can be enumerated. The core is finite; the registry is expandable.

Start here

Five-step quick start

1. Fill the intake in 20-audit-report-template.md: target, executive, domain, industry, region/jurisdictions, offered services, dates, and currency.
2. Select an engagement mode from 00-system-charter.md and an expansion profile from 10-query-pattern-library.md.
3. Run the Coordinator in 19-agent-prompts.md; route the phase prompts and preserve the shared evidence/claim/model registries.
4. Assemble only reviewed outputs in 20-audit-report-template.md; leave unknowns blank or mark [U], and use not estimable when financial inputs are missing.
5. Run every applicable gate in 21-quality-control-tests.md, obtain human release approval, and only then consider a separately authorized CRM or outreach action.

The tool catalogs were verified at the library research baseline. Before production, create version-pinned registry entries for every selected repository, model, API, hosted tier, and source—recording commit/release, terms version, quota, commercial-use decision, and verification date.

Mandatory operating rules

• Passive public-source research is the default. No login bypass, exploitation, credential collection, intrusive scanning, pretexting, or contact-data guessing.
• A source is not a finding. Preserve its URL, publication/observation time, retrieval time, excerpt or structured fact, and content hash where practical.
• Keep Observed, Calculated, Inferred, Hypothesized, Unknown, and Contradicted separate.
• Never present an inferred security weakness, executive motive, revenue figure, sentiment percentage, or causal effect as observed fact.
• Dollar values are low/base/high scenarios with visible formulas and inputs. If inputs are unavailable, say not estimable and list the missing inputs.
• Respect robots.txt, source terms, API limits, privacy law, retention limits, and opt-outs. Public visibility does not automatically authorize collection or marketing use.
• Outreach uses business-relevant findings. It excludes family, home, health, protected traits, private routines, leaked credentials, and other sensitive personal details.
• The system may suggest a likely corporate email pattern, but the CRM must distinguish published, verified, pattern-only, and unknown. Never claim a guessed address is verified.
• Human review gates all high-impact claims, security findings, named-person profiles, financial estimates, and outbound messages.

Completion definition

An audit is complete only when:

• every required nine-phase module is complete or carries a reasoned N/A/Unknown;
• all material findings are supported by evidence records;
• every critical feature or risk is checked against all fourteen change variables, with non-applicable variables explained;
• baseline, boundary, contradiction, and failure states have been tested;
• financial ranges reconcile and do not double count;
• competitor comparisons use like-for-like time windows and measures;
• personal and outreach data passes privacy, relevance, and consent/legitimate-use review;
• the executive brief states limitations and missing evidence.

Output bundle

The primary outputs are:

• an executive briefing;
• a source and claim ledger;
• marketing, PR, technical, economic, and competitor findings;
• a financial-impact matrix;
• a ranked opportunity portfolio;
• a C-suite outreach blueprint;
• a sanitized CRM import table;
• a research backlog describing what would change the conclusions.

This library is strategic and technical guidance, not legal, investment, or penetration-testing advice.

---

README.md · 92 lines · 6151 bytes · SHA-256 cd5578b40ccf8678