30 finite pages · released 2026-08-18
Corporate charts begin with evidence, not a convenient date
This library defines how organization events are selected, timed, located, calculated, reviewed, and tested. The case studies are sanitized system demonstrations—not client outcomes and not evidence that astrology predicts business results.
Event-specific
Formation, payment, deployment, launch, merger, and acquisition records remain distinct instead of becoming one universal company birth.
Evidence-bound
Every timestamp, location basis, confidence class, evidence locator, and calculation convention remains inspectable.
No outcome guarantee
No page infers valuation, investment return, legal status, revenue, survival, adoption, or a guaranteed future event.
Methodology
15 pages
Organization-event taxonomy for corporate charts
Why filing, acceptance, certification, transaction, deployment, launch, merger, and acquisition events must remain distinct corporate chart inputs.
Selecting a legal formation event
How filing submission, filing acceptance, and certificate issuance are separated when constructing an evidence-bound legal formation chart.
First commercial transaction as an organization event
A method for recording the first compensated transaction without confusing authorization, ledger posting, settlement, payout, or bank receipt.
First production deployment as a corporate event
How to distinguish code merge, build, release creation, deployment start, regional completion, first request, and customer availability.
Public launch event methodology
A reproducible policy for launch events spanning publication, announcement, DNS propagation, application availability, and first public access.
Merger and acquisition event methodology
How signing, regulatory approval, shareholder approval, legal effectiveness, and financial close are retained as distinct organization events.
Event-time confidence and uncertainty intervals
How recorded instants, minutes, hours, official dates, and estimates become explicit uncertainty windows instead of false precision.
Date-only corporate chart stability audit
A fail-closed procedure for deciding which placements survive a full-day event-time window and which houses or limbs must be withheld.
Corporate event-location selection policy
How authority, registered office, operational, transaction, deployment, and closing locations are selected without silent substitution.
Jurisdiction versus event location
Why legal jurisdiction, registration authority, registered office, operational city, and computational observer must remain separate fields.
Evidence attachment fingerprinting without content retention
How SHA-256, byte length, media type, filename, and locator preserve reproducibility while raw private evidence remains outside the report.
Civil-time resolution for organization events
How local timestamps, IANA zones, UTC offsets, daylight-saving folds, gaps, and historical uncertainty become one reproducible time record.
Tropical and sidereal corporate chart comparison
A parallel-model method that shares one event and ephemeris while keeping tropical and Lahiri-sidereal labels, rules, and scores separate.
Organization-house stability and significator policy
When organization-specific whole-sign houses may be displayed and why unstable event times force house applications to be withheld.
Preregistering corporate timing outcomes
How a corporate timing hypothesis becomes a locked, measurable forecast instead of a retrospective story fitted to milestones.
Sanitized case studies
15 pages
These are synthetic, de-identified demonstrations of system behavior. They are not presented as real client engagements or successful forecasts.
Sanitized case study: Competing formation events remain separate
A sanitized record contains four plausible beginnings; the system refuses to choose one after inspecting their charts.
Sanitized case study: Filing submission versus registry acceptance
A sanitized legal-formation case separates a minute-level submission receipt from a later date-only acceptance record.
Sanitized case study: First platform credit with later payout
A sanitized income-origin case distinguishes platform account credit, payout initiation, and bank receipt.
Sanitized case study: Transaction location differs from registered office
A sanitized remote-business case documents why transaction location and registered office cannot be silently interchanged.
Sanitized case study: Deployment region as a documented location exception
A sanitized distributed-system case uses a provider region only because the deployment event occurred there under a declared policy.
Sanitized case study: Corporate event during a daylight-saving fold
A sanitized automated event occurs in a repeated local hour that maps to two valid UTC instants.
Sanitized case study: Historical timezone uncertainty in an institutional record
A sanitized older institutional event has a recorded local time but uncertain historical clock practice.
Sanitized case study: Evidence digest without raw-document publication
A sanitized formation case proves which private attachment was used without exposing its content.
Sanitized case study: Production deployment versus public launch
A sanitized product case separates successful production deployment from later customer-facing availability.
Sanitized case study: Cross-jurisdiction merger event chain
A sanitized merger case contains approval, legal effect, and financial close across different jurisdictions and locations.
Sanitized case study: Parallel tropical and sidereal corporate comparison
A sanitized formation event is calculated in two zodiac frames without mixing labels or selecting the more compelling narrative.
Sanitized case study: Repeated ingress chronology around retrograde motion
A sanitized corporate milestone window contains three crossings of one zodiac boundary.
Sanitized case study: Ordinary non-event periods in a corporate corpus
A sanitized historical corpus pairs milestones with systematically sampled intervals in which the target event did not occur.
Sanitized case study: Outcome leakage causes forecast refusal
A sanitized benchmark attempt supplies a milestone whose outcome was already known before model registration.
Sanitized case study: Estimated event time changes house geometry
A sanitized operational milestone has a narrow-looking estimate that still crosses an ascendant boundary.