Good documentation should make the product understandable and trustworthy without publishing a turnkey clone of its operating system.
Publicly documented
- entity types and relationship meanings;
- evidence classes and provenance behavior;
- user-facing scores, windows and status semantics;
- product workflows and navigation;
- network-aware behavior visible in the current product;
- known limitations and correction paths.
Kept internal
- exact system and agent prompts;
- model routing policy and budget controls;
- scoring weights and production thresholds;
- anti-noise, abuse and identity heuristics;
- private graph schemas and review queues;
- provider credentials, deployment details and operational runbooks;
- source-specific operational controls.
Interpretation limits
WALPHA observes bounded data sources and can miss deleted posts, unavailable enrichment, private activity or emerging identities. Social attention is not sentiment, market quality or investment advice. Model findings can be wrong and should be evaluated against their cited evidence.
Corrections
Identity and relationship corrections should preserve the original evidence, record the reviewed outcome and update active product views. Public-facing correction mechanisms will mature with the beta.
Documentation status
These pages are a living product reference. Material changes to public entity semantics, evidence boundaries or integration behavior should update the documentation alongside the product change.