{"version":"astrology-workflows/1.0","preparedOn":"2026-09-04","status":"prepared-not-deployed","purpose":"Worked protocols for reproducible inputs, calculation receipts, prospective evaluation, falsifiability, and tradition-scoped comparison.","boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","counts":{"workflows":36,"calculationReceipts":10,"categories":{"input-reference-frame":12,"calculation-uncertainty":10,"evaluation-falsifiability":8,"tradition-comparison":6}},"workflows":[{"slug":"source-event-intake","category":"input-reference-frame","title":"Source-event intake and identity workflow","objective":"Convert a claimed birth, organization, or public event into a source-bound candidate before any celestial calculation begins.","requiredInputs":["Event type","Source record and issuer","Claimed local date and time","Location evidence","Competing candidate events"],"orderedSteps":["Classify the event without looking at chart output.","Fingerprint each source attachment and record its rights boundary.","Separate observed fields from inferred or user-supplied fields.","Retain competing event candidates instead of selecting a favorable chart.","Issue an intake manifest with unresolved fields explicit."],"outputs":["Event identity manifest","Evidence fingerprints","Uncertainty and competing-event list"],"refusalConditions":["No source or issuer is identified.","The event type was selected after chart inspection.","Confidential material would enter a public artifact."],"completionCriteria":["Every field has provenance.","Competing candidates remain visible.","No chart has yet been interpreted."],"authorityIds":["corporate:organization-event-taxonomy","corporate:evidence-attachment-fingerprinting","calculation:civil-time-to-utc"],"relatedAnswerSlugs":["information-needed-for-an-astrology-calculation","which-event-starts-a-corporate-chart"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"corporate:organization-event-taxonomy","family":"corporate","title":"Organization-event taxonomy for corporate charts","path":"/knowledge/astrology/corporate-mundane/organization-event-taxonomy","establishes":"Name the event before calculation, select one supported event type, preserve competing candidates, and prohibit retroactive substitution based on which chart looks more favorable. Each interpretation rule must declare the event types it can consume.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:evidence-attachment-fingerprinting","family":"corporate","title":"Evidence attachment fingerprinting without content retention","path":"/knowledge/astrology/corporate-mundane/evidence-attachment-fingerprinting","establishes":"Hash the attachment bytes in memory, validate media type and size limits, retain the SHA-256 digest and bounded metadata, and discard content unless a separate consent and retention policy authorizes storage.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"calculation:civil-time-to-utc","family":"calculation","title":"Converting local civil time to UTC","path":"/knowledge/astrology/calculations/civil-time-to-utc","establishes":"A local civil timestamp is a wall-clock label. It becomes a unique instant only after a timezone rule supplies an offset and any fold or gap is resolved.","boundary":"A precise UTC conversion does not make the source birth or event time accurate.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/source-event-intake"},{"slug":"civil-time-resolution","category":"input-reference-frame","title":"Local civil time to UTC workflow","objective":"Resolve a wall-clock label into a reproducible instant without hiding timezone rules.","requiredInputs":["Local ISO date","Local clock time","IANA timezone identifier","Pinned tzdb release","Fold or gap evidence"],"orderedSteps":["Validate the civil fields independently.","Load the named timezone rules.","Detect an ordinary time, fold, or gap.","Require a documented fold choice or gap correction.","Emit the offset and UTC instant together."],"outputs":["UTC instant","Resolved offset","Timezone-rule provenance"],"refusalConditions":["Only a current UTC offset is supplied.","A fold has two candidates and no policy.","A gap is silently shifted."],"completionCriteria":["The conversion reproduces under the pinned tzdb.","The civil input remains attached.","Ambiguity is resolved or retained."],"authorityIds":["calculation:civil-time-to-utc","calculation:iana-time-zone-identifiers","corporate:civil-time-resolution-for-organizations"],"relatedAnswerSlugs":["timezone-versus-utc-offset","daylight-saving-time-ambiguity"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:civil-time-to-utc","family":"calculation","title":"Converting local civil time to UTC","path":"/knowledge/astrology/calculations/civil-time-to-utc","establishes":"A local civil timestamp is a wall-clock label. It becomes a unique instant only after a timezone rule supplies an offset and any fold or gap is resolved.","boundary":"A precise UTC conversion does not make the source birth or event time accurate.","status":"production-contract"},{"id":"calculation:iana-time-zone-identifiers","family":"calculation","title":"IANA timezone identifiers and chart reproducibility","path":"/knowledge/astrology/calculations/iana-time-zone-identifiers","establishes":"An IANA timezone identifier names a versioned sequence of civil-time rules, including historical offset changes and daylight-saving transitions.","boundary":"A timezone identifier does not prove where an event occurred or which local clock was consulted.","status":"production-contract"},{"id":"corporate:civil-time-resolution-for-organizations","family":"corporate","title":"Civil-time resolution for organization events","path":"/knowledge/astrology/corporate-mundane/civil-time-resolution-for-organizations","establishes":"Resolve the local timestamp with a pinned IANA zone, detect folds and gaps, retain selected offset and tzdb version, reject silent normalization, and expand uncertain historical records into candidate instants.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/civil-time-resolution"},{"slug":"timezone-fold-gap-triage","category":"input-reference-frame","title":"Timezone fold and gap triage","objective":"Branch repeated, nonexistent, and ordinary local times into explicit resolution paths.","requiredInputs":["Local timestamp","IANA zone","tzdb version","Source precision"],"orderedSteps":["Resolve all candidate offsets.","Classify zero candidates as a gap, two as a fold, and one as ordinary.","For a fold retain both instants unless evidence selects one.","For a gap require a source correction rather than runtime normalization.","Run sensitivity across every retained instant."],"outputs":["Temporal classification","Candidate-instant set","Sensitivity requirement"],"refusalConditions":["The runtime default chooses a fold.","A gap is coerced without provenance.","Only the preferred chart is retained."],"completionCriteria":["All candidate instants are enumerated.","Selection evidence is attached.","Downstream consumers accept a set, not an assumed scalar."],"authorityIds":["calculation:daylight-saving-folds","calculation:daylight-saving-gaps","calculation:civil-time-to-utc"],"relatedAnswerSlugs":["daylight-saving-time-ambiguity","why-exact-time-matters"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:daylight-saving-folds","family":"calculation","title":"Daylight-saving folds: one clock time, two instants","path":"/knowledge/astrology/calculations/daylight-saving-folds","establishes":"A fold is a backward offset transition that maps two distinct UTC instants to the same local date and clock time.","boundary":"Choosing the chart that appears more favorable is not evidence about which occurrence the source meant.","status":"production-contract"},{"id":"calculation:daylight-saving-gaps","family":"calculation","title":"Daylight-saving gaps: local times that never occurred","path":"/knowledge/astrology/calculations/daylight-saving-gaps","establishes":"A gap is a forward offset transition that leaves a range of local clock labels with no corresponding UTC instant.","boundary":"A software-repaired timestamp is not an observed event time.","status":"production-contract"},{"id":"calculation:civil-time-to-utc","family":"calculation","title":"Converting local civil time to UTC","path":"/knowledge/astrology/calculations/civil-time-to-utc","establishes":"A local civil timestamp is a wall-clock label. It becomes a unique instant only after a timezone rule supplies an offset and any fold or gap is resolved.","boundary":"A precise UTC conversion does not make the source birth or event time accurate.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/timezone-fold-gap-triage"},{"slug":"uncertain-time-interval","category":"input-reference-frame","title":"Uncertain-time interval construction","objective":"Represent imprecise event time as a bounded interval and feature-stability problem.","requiredInputs":["Earliest defensible instant","Latest defensible instant","Evidence for each bound","Requested chart features"],"orderedSteps":["Reject false minute precision.","Construct a closed uncertainty interval.","Evaluate each requested feature across the interval.","Retain stable features and withhold unstable ones.","Version a new interval only when new evidence arrives."],"outputs":["Time interval","Feature stability table","Withheld-feature list"],"refusalConditions":["A midpoint is presented as observed.","Rectification is treated as source evidence.","No basis exists for either interval bound."],"completionCriteria":["Every feature is stable or withheld.","Interval provenance is explicit.","No precise-looking chart overrides the source."],"authorityIds":["calculation:historical-time-zone-uncertainty","corporate:event-time-confidence-method","corporate:date-only-stability-audit"],"relatedAnswerSlugs":["what-to-do-when-birth-time-is-unknown","corporate-event-time-uncertainty"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:historical-time-zone-uncertainty","family":"calculation","title":"Historical timezone uncertainty","path":"/knowledge/astrology/calculations/historical-time-zone-uncertainty","establishes":"Historical civil time is reconstructed evidence, not a timeless mapping. A database rule can be precise while the underlying historical record remains uncertain.","boundary":"Modern software precision cannot recover information absent from the historical record.","status":"production-contract"},{"id":"corporate:event-time-confidence-method","family":"corporate","title":"Event-time confidence and uncertainty intervals","path":"/knowledge/astrology/corporate-mundane/event-time-confidence-method","establishes":"Assign a confidence class from the evidence, convert it to a bounded interval, choose a representative instant only for calculation, and recompute time-sensitive features across the full possible interval.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:date-only-stability-audit","family":"corporate","title":"Date-only corporate chart stability audit","path":"/knowledge/astrology/corporate-mundane/date-only-stability-audit","establishes":"Calculate at the representative midpoint and both interval edges, sample intermediate instants where necessary, compare ascendant, whole-sign houses, and pañcāṅga limbs, and publish only features stable across the declared window.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/uncertain-time-interval"},{"slug":"observer-site-contract","category":"input-reference-frame","title":"Observer site and horizon contract","objective":"Turn a place label into the geodetic inputs required for observer-dependent geometry.","requiredInputs":["Latitude","Longitude","Elevation","Coordinate datum","Horizon and atmosphere policy"],"orderedSteps":["Geocode without discarding the original place evidence.","Record signed coordinates and datum.","Declare geocentric or topocentric origin.","Apply elevation only where the method consumes it.","Keep terrain and refraction limitations explicit."],"outputs":["Observer contract","Origin declaration","Horizon limitations"],"refusalConditions":["A city centroid is described as the event site.","Coordinate signs or datum are absent.","Local obstruction is inferred from ideal geometry."],"completionCriteria":["Coordinates round-trip exactly.","Origin is declared.","Observer-sensitive outputs cite this contract."],"authorityIds":["calculation:observer-latitude-longitude","calculation:elevation-and-horizon","calculation:geocentric-vs-topocentric"],"relatedAnswerSlugs":["topocentric-versus-geocentric-chart","jurisdiction-versus-event-location"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:observer-latitude-longitude","family":"calculation","title":"Observer latitude and longitude","path":"/knowledge/astrology/calculations/observer-latitude-longitude","establishes":"Observer coordinates locate the calculation origin on Earth. Longitude sets local rotation angle; latitude sets the horizon orientation.","boundary":"A geocoder result does not prove the person or event was physically at that point.","status":"production-contract"},{"id":"calculation:elevation-and-horizon","family":"calculation","title":"Elevation, horizon, and rise/set calculations","path":"/knowledge/astrology/calculations/elevation-and-horizon","establishes":"Elevation changes the observer position and visible horizon. Atmospheric refraction and terrain obstruction are separate corrections.","boundary":"A computed standard sunrise is not necessarily the first locally visible light over terrain.","status":"production-contract"},{"id":"calculation:geocentric-vs-topocentric","family":"calculation","title":"Geocentric versus topocentric positions","path":"/knowledge/astrology/calculations/geocentric-vs-topocentric","establishes":"Geocentric coordinates use Earth’s center as origin; topocentric coordinates use a specified observing site on or near Earth’s surface.","boundary":"Topocentric output is not intrinsically more appropriate for every astrological tradition.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/observer-site-contract"},{"slug":"timescale-conversion-chain","category":"input-reference-frame","title":"UTC–TAI–TT–TDB–UT1 conversion chain","objective":"Declare which time scale each operation consumes and preserve every conversion input.","requiredInputs":["UTC instant","Leap-second table version","Earth-orientation data version","Ephemeris time-scale requirement"],"orderedSteps":["Start from the resolved UTC provenance unit.","Apply the pinned leap-second relation to TAI.","Derive TT under the declared convention.","Use TDB only where the ephemeris requires it.","Use UT1 only with named Earth-orientation data."],"outputs":["Time-scale chain","Versioned offsets","Unavailable-conversion warnings"],"refusalConditions":["UTC and UT1 are treated as synonyms.","Leap-second or Earth-orientation versions are missing.","A scale is converted because its label looks similar."],"completionCriteria":["Every scale has a purpose.","Every offset is reproducible.","Unavailable data yields refusal or bounded uncertainty."],"authorityIds":["calculation:utc-tai-tt-tdb-ut1","calculation:leap-seconds","calculation:julian-date"],"relatedAnswerSlugs":["information-needed-for-an-astrology-calculation","how-to-audit-a-chart-calculation"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:utc-tai-tt-tdb-ut1","family":"calculation","title":"UTC, TAI, TT, TDB, and UT1","path":"/knowledge/astrology/calculations/utc-tai-tt-tdb-ut1","establishes":"UTC is civil time, TAI is atomic time, TT is terrestrial dynamical time, TDB is a barycentric coordinate time, and UT1 follows measured Earth rotation.","boundary":"Changing a time scale is a coordinate conversion, not an astrological technique.","status":"production-contract"},{"id":"calculation:leap-seconds","family":"calculation","title":"Leap seconds and celestial timestamps","path":"/knowledge/astrology/calculations/leap-seconds","establishes":"A leap second changes the offset between UTC and atomic time so civil time remains close to Earth rotation.","boundary":"Leap-second correctness does not improve an event timestamp that was only recorded to the minute or day.","status":"production-contract"},{"id":"calculation:julian-date","family":"calculation","title":"Julian Date conventions","path":"/knowledge/astrology/calculations/julian-date","establishes":"Julian Date is a continuous day number whose integer boundary occurs at noon; Modified Julian Date uses a different offset and midnight boundary.","boundary":"A Julian Date is only a time coordinate and carries no interpretive meaning.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/timescale-conversion-chain"},{"slug":"ephemeris-model-pinning","category":"input-reference-frame","title":"Ephemeris and correction-model pinning","objective":"Bind positions to one identified ephemeris, data release, software version, and correction chain.","requiredInputs":["Ephemeris identifier","Data/kernel version","Software version","Geometric/apparent policy","Precision target"],"orderedSteps":["Name the ephemeris before calculation.","Record all data kernels or package versions.","Declare geometric, astrometric, or apparent output.","Pin light-time, aberration, and deflection policy.","Hash the complete calculation dependency manifest."],"outputs":["Dependency manifest","Correction-model declaration","Dependency digest"],"refusalConditions":["Only a product name is supplied.","Apparent and geometric values are mixed.","The dependency digest cannot be reproduced."],"completionCriteria":["A second implementation knows what to reproduce.","Corrections are not implicit.","Version changes create a new receipt."],"authorityIds":["calculation:ephemeris-versioning","calculation:apparent-astrometric-geometric","calculation:light-time-aberration-deflection"],"relatedAnswerSlugs":["why-astrology-software-disagrees","how-to-audit-a-chart-calculation"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:ephemeris-versioning","family":"calculation","title":"Ephemeris and software versioning","path":"/knowledge/astrology/calculations/ephemeris-versioning","establishes":"An ephemeris result depends on the numerical model, data release, software implementation, configuration, and fallback behavior.","boundary":"Using a respected ephemeris does not validate claims derived from astrological labels.","status":"production-contract"},{"id":"calculation:apparent-astrometric-geometric","family":"calculation","title":"Geometric, astrometric, and apparent positions","path":"/knowledge/astrology/calculations/apparent-astrometric-geometric","establishes":"Geometric positions omit light propagation; astrometric positions account for light time in a specified frame; apparent positions add observer-oriented effects such as aberration and deflection according to the model.","boundary":"“Apparent” does not mean visually observable or astrologically effective.","status":"production-contract"},{"id":"calculation:light-time-aberration-deflection","family":"calculation","title":"Light time, aberration, and gravitational deflection","path":"/knowledge/astrology/calculations/light-time-aberration-deflection","establishes":"Light time accounts for propagation delay; stellar aberration accounts for observer velocity; gravitational deflection accounts for light-path bending in gravitational fields.","boundary":"A physically corrected coordinate has no greater empirical support as an astrological predictor.","status":"validation-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/ephemeris-model-pinning"},{"slug":"coordinate-origin-selection","category":"input-reference-frame","title":"Geocentric or topocentric origin selection","objective":"Choose coordinate origin from the requested observable rather than from interpretive preference.","requiredInputs":["Requested observable","Celestial body","Observer contract when local","Shared instant and ephemeris"],"orderedSteps":["Classify the output as Earth-center or observer-relative.","Require an observer for topocentric work.","Hold instant and ephemeris constant across comparisons.","Calculate both origins only when the protocol asks for a comparison.","Label each output at the field level."],"outputs":["Origin decision","Eligible input set","Parallel positions when requested"],"refusalConditions":["Topocentric output lacks an observer.","Origin changes after seeing a sign label.","Two origins are averaged."],"completionCriteria":["Every position names its origin.","Shared inputs are frozen.","No interpretation chooses the geometry."],"authorityIds":["calculation:geocentric-vs-topocentric","calculation:observer-latitude-longitude","calculation:elevation-and-horizon"],"relatedAnswerSlugs":["topocentric-versus-geocentric-chart","why-astrology-software-disagrees"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:geocentric-vs-topocentric","family":"calculation","title":"Geocentric versus topocentric positions","path":"/knowledge/astrology/calculations/geocentric-vs-topocentric","establishes":"Geocentric coordinates use Earth’s center as origin; topocentric coordinates use a specified observing site on or near Earth’s surface.","boundary":"Topocentric output is not intrinsically more appropriate for every astrological tradition.","status":"production-contract"},{"id":"calculation:observer-latitude-longitude","family":"calculation","title":"Observer latitude and longitude","path":"/knowledge/astrology/calculations/observer-latitude-longitude","establishes":"Observer coordinates locate the calculation origin on Earth. Longitude sets local rotation angle; latitude sets the horizon orientation.","boundary":"A geocoder result does not prove the person or event was physically at that point.","status":"production-contract"},{"id":"calculation:elevation-and-horizon","family":"calculation","title":"Elevation, horizon, and rise/set calculations","path":"/knowledge/astrology/calculations/elevation-and-horizon","establishes":"Elevation changes the observer position and visible horizon. Atmospheric refraction and terrain obstruction are separate corrections.","boundary":"A computed standard sunrise is not necessarily the first locally visible light over terrain.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/coordinate-origin-selection"},{"slug":"reference-frame-declaration","category":"input-reference-frame","title":"Coordinate reference-frame declaration","objective":"Specify axes, origin, epoch, equinox, and correction state before comparing coordinates.","requiredInputs":["Coordinate family","Origin","Epoch/equinox","Mean/true policy","Geometric/apparent policy"],"orderedSteps":["Name ecliptic, equatorial, or horizon coordinates.","Attach the origin.","Record epoch and equinox separately.","Declare mean or true orientation.","Transform only through a named operation."],"outputs":["Reference-frame contract","Allowed transformations","Comparison refusal list"],"refusalConditions":["Longitude fields omit their frame.","Epoch and equinox are conflated.","Coordinates from different frames are subtracted directly."],"completionCriteria":["Every coordinate is self-describing.","Transform order is reproducible.","Frame mismatch fails before interpretation."],"authorityIds":["calculation:ecliptic-vs-equatorial","calculation:epoch-equinox-and-frame","calculation:nutation-true-vs-mean"],"relatedAnswerSlugs":["why-astrology-software-disagrees","tropical-versus-sidereal-zodiac"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:ecliptic-vs-equatorial","family":"calculation","title":"Ecliptic versus equatorial coordinates","path":"/knowledge/astrology/calculations/ecliptic-vs-equatorial","establishes":"Ecliptic coordinates use an ecliptic plane and pole; equatorial coordinates use an equator and celestial pole. Their relation depends on epoch, ecliptic definition, and obliquity model.","boundary":"Coordinate representation does not change the physical configuration or validate zodiac symbolism.","status":"production-contract"},{"id":"calculation:epoch-equinox-and-frame","family":"calculation","title":"Reference frame, epoch, and equinox","path":"/knowledge/astrology/calculations/epoch-equinox-and-frame","establishes":"A frame defines axes, an epoch identifies a reference time, and an equinox can identify the origin and orientation used for equatorial or ecliptic coordinates.","boundary":"A standardized reference frame is a measurement convention, not an interpretive tradition.","status":"production-contract"},{"id":"calculation:nutation-true-vs-mean","family":"calculation","title":"Nutation and true versus mean coordinates","path":"/knowledge/astrology/calculations/nutation-true-vs-mean","establishes":"Mean coordinates include precession without short-period nutation; true coordinates include the selected nutation model.","boundary":"True coordinates are not “truer astrology”; the word identifies an astronomical correction convention.","status":"validation-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/reference-frame-declaration"},{"slug":"zodiac-zero-point-declaration","category":"input-reference-frame","title":"Zodiac zero-point declaration","objective":"Derive tropical and sidereal labels from one retained celestial state without blending conventions.","requiredInputs":["Tropical ecliptic longitude","Tropical or named sidereal frame","Ayanāṁśa method and version when sidereal","Boundary policy"],"orderedSteps":["Retain the unrounded tropical longitude.","Declare the requested zodiac frame.","Apply the named offset only to the sidereal field.","Normalize the result into [0,360).","Report distance to the next sign boundary."],"outputs":["Frame-specific longitude","Sign label","Boundary distance"],"refusalConditions":["The word sidereal appears without a convention.","Tropical and sidereal labels overwrite one field.","The offset is chosen after interpretation."],"completionCriteria":["Both source and derived values remain available.","The convention is versioned.","Boundary instability is visible."],"authorityIds":["calculation:tropical-zodiac-longitude","calculation:sidereal-zodiac-longitude","calculation:lahiri-ayanamsa-convention"],"relatedAnswerSlugs":["tropical-versus-sidereal-zodiac","what-is-an-ayanamsha"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:tropical-zodiac-longitude","family":"calculation","title":"Tropical zodiac longitude","path":"/knowledge/astrology/calculations/tropical-zodiac-longitude","establishes":"Tropical zodiac longitude divides an ecliptic-of-date coordinate into twelve 30° sectors beginning at the adopted March equinox direction.","boundary":"Calling a sector Aries or Cancer does not scientifically establish traits or future events.","status":"production-contract"},{"id":"calculation:sidereal-zodiac-longitude","family":"calculation","title":"Sidereal zodiac longitude","path":"/knowledge/astrology/calculations/sidereal-zodiac-longitude","establishes":"Sidereal zodiac longitude is a tropical ecliptic longitude transformed by a selected stellar-reference offset called an ayanāṁśa.","boundary":"A sidereal conversion does not show that one astrological system is empirically superior.","status":"production-contract"},{"id":"calculation:lahiri-ayanamsa-convention","family":"calculation","title":"Lahiri ayanāṁśa convention","path":"/knowledge/astrology/calculations/lahiri-ayanamsa-convention","establishes":"Lahiri ayanāṁśa is one named sidereal zero-point convention; it supplies the angular offset subtracted from tropical longitude.","boundary":"Lahiri selection defines chart coordinates; it does not validate Jyotiṣa predictions.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/zodiac-zero-point-declaration"},{"slug":"house-system-eligibility","category":"input-reference-frame","title":"House-system eligibility workflow","objective":"Determine whether an event has enough observer and time evidence for the requested house system.","requiredInputs":["UTC instant or interval","Observer coordinates","House-system identifier","Polar-latitude policy"],"orderedSteps":["Validate time and location provenance.","Compute ascendant and midheaven under the shared frame.","Check the requested system at the observer latitude.","Sweep uncertain time across all cusps.","Withhold houses when cusps or system validity fail."],"outputs":["House-system eligibility","Cusp stability table","Withheld-output reasons"],"refusalConditions":["Unknown time is replaced by noon.","A polar limitation is ignored.","Different systems are blended into one house number."],"completionCriteria":["The system is named.","Every cusp is stable or withheld.","Observer dependence is explicit."],"authorityIds":["calculation:ascendant","calculation:whole-sign-houses","calculation:placidus-houses","calculation:polar-house-limitations"],"relatedAnswerSlugs":["ascendant-and-whole-sign-houses","why-house-systems-disagree"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:ascendant","family":"calculation","title":"Ascendant calculation","path":"/knowledge/astrology/calculations/ascendant","establishes":"The ascendant is the ecliptic longitude at the eastern intersection of the local astronomical horizon and ecliptic at a specified instant and observer.","boundary":"An exact ascendant does not establish personality or destiny.","status":"production-contract"},{"id":"calculation:whole-sign-houses","family":"calculation","title":"Whole-sign house assignment","path":"/knowledge/astrology/calculations/whole-sign-houses","establishes":"Whole-sign houses divide the zodiac into twelve sign sectors; the sign containing the ascendant becomes the first house regardless of ascendant degree.","boundary":"Whole-sign simplicity does not prove the associated house interpretations.","status":"production-contract"},{"id":"calculation:placidus-houses","family":"calculation","title":"Placidus house convention","path":"/knowledge/astrology/calculations/placidus-houses","establishes":"Placidus is a time-proportional quadrant system whose intermediate cusps are derived from diurnal motion between angular positions.","boundary":"Placidus and whole-sign charts must be evaluated as separate declared models, not averaged.","status":"comparison-only"},{"id":"calculation:polar-house-limitations","family":"calculation","title":"Polar latitude limitations in house calculation","path":"/knowledge/astrology/calculations/polar-house-limitations","establishes":"High-latitude geometry can remove daily rise/set events and make specific time-division house equations undefined, while the ecliptic and horizon still intersect.","boundary":"Polar exceptions do not justify inventing an event time or forcing an auspiciousness score.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/house-system-eligibility"},{"slug":"canonical-input-manifest","category":"input-reference-frame","title":"Canonical chart-input manifest","objective":"Freeze all calculation choices into one digest-bound input object before interpretation.","requiredInputs":["Event manifest","Time-scale chain","Observer contract","Ephemeris manifest","Frame, zodiac, and house policies"],"orderedSteps":["Normalize Unicode and explicit numeric strings.","Sort object keys by code unit through the shared canonicalizer.","Reject non-finite or undeclared values.","Compute one manifest digest.","Pass only the verified manifest to calculations."],"outputs":["Canonical JSON input","Input digest","Versioned dependency references"],"refusalConditions":["Hidden defaults remain.","A mutable value is excluded from the digest.","Interpretive text is inserted into calculation input."],"completionCriteria":["Independent canonicalization yields identical bytes.","Any covered mutation moves the digest.","No secret or personal field enters a public registry."],"authorityIds":["calculation:reproducibility-digests","calculation:precision-rounding-and-uncertainty","corporate:evidence-attachment-fingerprinting"],"relatedAnswerSlugs":["how-to-audit-a-chart-calculation","information-needed-for-an-astrology-calculation"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:reproducibility-digests","family":"calculation","title":"Reproducibility digests and calculation provenance","path":"/knowledge/astrology/calculations/reproducibility-digests","establishes":"A digest is a cryptographic hash of canonical serialized data. It detects change but does not by itself prove that the data were true.","boundary":"A valid digest proves integrity relative to its hashed bytes, not scientific validity or authorship.","status":"production-contract"},{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"},{"id":"corporate:evidence-attachment-fingerprinting","family":"corporate","title":"Evidence attachment fingerprinting without content retention","path":"/knowledge/astrology/corporate-mundane/evidence-attachment-fingerprinting","establishes":"Hash the attachment bytes in memory, validate media type and size limits, retain the SHA-256 digest and bounded metadata, and discard content unless a separate consent and retention policy authorizes storage.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/canonical-input-manifest"},{"slug":"julian-date-receipt","category":"calculation-uncertainty","title":"Julian-date conversion receipt","objective":"Convert an explicit UTC instant to Julian Date under a declared scale and preserve the arithmetic.","requiredInputs":["Explicit UTC instant","Time-scale label","Conversion constant","Precision policy"],"orderedSteps":["Validate the UTC serialization.","Convert Unix milliseconds to days.","Add the Unix-epoch Julian Date constant.","Round only for display.","Digest inputs, units, assumptions, and output."],"outputs":["Julian Date","Calculation receipt","Scale and precision declaration"],"refusalConditions":["The instant lacks an offset.","UTC is silently relabelled TT or TDB.","Displayed rounding replaces retained precision."],"completionCriteria":["The fixture recomputes.","A changed instant moves the digest.","The output names its time scale."],"authorityIds":["calculation:julian-date","calculation:utc-tai-tt-tdb-ut1"],"relatedAnswerSlugs":["information-needed-for-an-astrology-calculation","how-to-audit-a-chart-calculation"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:julian-date","family":"calculation","title":"Julian Date conventions","path":"/knowledge/astrology/calculations/julian-date","establishes":"Julian Date is a continuous day number whose integer boundary occurs at noon; Modified Julian Date uses a different offset and midnight boundary.","boundary":"A Julian Date is only a time coordinate and carries no interpretive meaning.","status":"production-contract"},{"id":"calculation:utc-tai-tt-tdb-ut1","family":"calculation","title":"UTC, TAI, TT, TDB, and UT1","path":"/knowledge/astrology/calculations/utc-tai-tt-tdb-ut1","establishes":"UTC is civil time, TAI is atomic time, TT is terrestrial dynamical time, TDB is a barycentric coordinate time, and UT1 follows measured Earth rotation.","boundary":"Changing a time scale is a coordinate conversion, not an astrological technique.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"julian-date","inputs":{"instantUtc":"2000-01-01T12:00:00.000Z"},"units":{"instantUtc":"UTC","julianDateUtc":"days"},"assumptions":["Unix epoch corresponds to JD 2440587.5 on the UTC scale for this fixture."],"outputs":{"julianDateUtc":"2451545"},"uncertainty":"Exact for the serialized fixture under its declared UTC-to-day arithmetic; it is not a TT or TDB ephemeris time.","receiptSha256":"sha256:44af2be623ac392a305eddbdb037f473f6fdbba7f9808534d3f4feee7c8e991c"},"path":"/knowledge/astrology/protocols/julian-date-receipt"},{"slug":"longitude-normalization-receipt","category":"calculation-uncertainty","title":"Longitude normalization receipt","objective":"Map an angular longitude into the half-open [0°,360°) interval without losing the original value.","requiredInputs":["Unnormalized longitude","Angular unit","Half-open interval policy","Retained precision"],"orderedSteps":["Validate a finite angle.","Apply modulo 360.","Add 360 to negative remainders.","Apply modulo again.","Retain input and output in the receipt."],"outputs":["Normalized longitude","Original longitude","Calculation receipt"],"refusalConditions":["The input is non-finite.","Radians are supplied as degrees.","360° and 0° are treated as different directions."],"completionCriteria":["Output is at least 0° and below 360°.","Equivalent rotations normalize identically.","Input mutation moves the digest."],"authorityIds":["calculation:longitude-normalization","calculation:precision-rounding-and-uncertainty"],"relatedAnswerSlugs":["what-is-an-ayanamsha","sign-boundary-uncertainty"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:longitude-normalization","family":"calculation","title":"Longitude normalization and angular difference","path":"/knowledge/astrology/calculations/longitude-normalization","establishes":"Normalized longitude maps any angle to [0°, 360°). Signed angular difference maps a displacement to a declared interval such as (−180°, 180°].","boundary":"Correct modular arithmetic classifies geometry only; it adds no interpretive evidence.","status":"production-contract"},{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"normalize-longitude","inputs":{"longitudeDegrees":"-15"},"units":{"longitudeDegrees":"degrees","normalizedDegrees":"degrees"},"assumptions":["The normalized interval is [0,360)."],"outputs":{"normalizedDegrees":"345"},"uncertainty":"No model uncertainty is introduced; floating-point and upstream coordinate uncertainty remain external inputs.","receiptSha256":"sha256:80dfe88e0c2271493887a1c01840b9dc2f5c9778517ab3bc5294b487520d1ff9"},"path":"/knowledge/astrology/protocols/longitude-normalization-receipt"},{"slug":"sidereal-transform-receipt","category":"calculation-uncertainty","title":"Tropical-to-sidereal transform receipt","objective":"Apply a named angular offset while retaining both coordinate values.","requiredInputs":["Tropical longitude","Ayanāṁśa value","Ayanāṁśa method and version","Epoch"],"orderedSteps":["Validate both angles.","Subtract the declared offset.","Normalize the result.","Retain tropical and sidereal values separately.","Digest the complete transform."],"outputs":["Sidereal longitude","Applied offset","Calculation receipt"],"refusalConditions":["The offset convention is unnamed.","The tropical value is overwritten.","The offset is inferred from a desired sign."],"completionCriteria":["Subtraction and normalization reproduce.","Method/version remain attached.","Boundary distance can be calculated downstream."],"authorityIds":["calculation:tropical-zodiac-longitude","calculation:sidereal-zodiac-longitude","calculation:lahiri-ayanamsa-convention"],"relatedAnswerSlugs":["what-is-an-ayanamsha","tropical-versus-sidereal-zodiac"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:tropical-zodiac-longitude","family":"calculation","title":"Tropical zodiac longitude","path":"/knowledge/astrology/calculations/tropical-zodiac-longitude","establishes":"Tropical zodiac longitude divides an ecliptic-of-date coordinate into twelve 30° sectors beginning at the adopted March equinox direction.","boundary":"Calling a sector Aries or Cancer does not scientifically establish traits or future events.","status":"production-contract"},{"id":"calculation:sidereal-zodiac-longitude","family":"calculation","title":"Sidereal zodiac longitude","path":"/knowledge/astrology/calculations/sidereal-zodiac-longitude","establishes":"Sidereal zodiac longitude is a tropical ecliptic longitude transformed by a selected stellar-reference offset called an ayanāṁśa.","boundary":"A sidereal conversion does not show that one astrological system is empirically superior.","status":"production-contract"},{"id":"calculation:lahiri-ayanamsa-convention","family":"calculation","title":"Lahiri ayanāṁśa convention","path":"/knowledge/astrology/calculations/lahiri-ayanamsa-convention","establishes":"Lahiri ayanāṁśa is one named sidereal zero-point convention; it supplies the angular offset subtracted from tropical longitude.","boundary":"Lahiri selection defines chart coordinates; it does not validate Jyotiṣa predictions.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"sidereal-transform","inputs":{"tropicalDegrees":"120","ayanamsaDegrees":"24"},"units":{"tropicalDegrees":"degrees","ayanamsaDegrees":"degrees","siderealDegrees":"degrees"},"assumptions":["The supplied 24° offset is a fixture, not a claim about an epoch or official ayanāṁśa value."],"outputs":{"siderealDegrees":"96"},"uncertainty":"The fixture arithmetic is deterministic; real uncertainty inherits the ephemeris and selected ayanāṁśa implementation.","receiptSha256":"sha256:9a81eceeb3f6ec39f6d867748316b876fb83b6c2061736450d8d0f5ab57ea6ab"},"path":"/knowledge/astrology/protocols/sidereal-transform-receipt"},{"slug":"sign-boundary-distance","category":"calculation-uncertainty","title":"Sign-boundary distance workflow","objective":"Quantify whether rounding or upstream uncertainty can change a derived sign label.","requiredInputs":["Unrounded frame-specific longitude","Angular uncertainty","30° sign partition","Precision policy"],"orderedSteps":["Normalize the longitude.","Compute position within its 30° interval.","Measure the nearest boundary distance.","Compare distance with total uncertainty.","Mark the label stable or unstable."],"outputs":["Nearest-boundary distance","Stability flag","Calculation receipt"],"refusalConditions":["Only a rounded sign label is available.","Uncertainty is omitted.","A boundary crossing is forced to one side."],"completionCriteria":["Distance recomputes.","Stability uses retained precision.","Unstable labels remain explicitly unstable."],"authorityIds":["calculation:zodiac-sign-boundaries","calculation:precision-rounding-and-uncertainty"],"relatedAnswerSlugs":["sign-boundary-uncertainty","why-astrology-software-disagrees"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:zodiac-sign-boundaries","family":"calculation","title":"Zodiac sign boundary sensitivity","path":"/knowledge/astrology/calculations/zodiac-sign-boundaries","establishes":"A sign is a floor-based classification of normalized longitude into twelve 30° intervals; the continuous longitude is the underlying calculated fact.","boundary":"A stable sign classification does not make its interpretation empirically supported.","status":"production-contract"},{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"sign-boundary-distance","inputs":{"longitudeDegrees":"29.9"},"units":{"longitudeDegrees":"degrees","lowerBoundaryDistanceDegrees":"degrees","nearestBoundaryDistanceDegrees":"degrees"},"assumptions":["Signs are half-open 30° intervals beginning at 0°."],"outputs":{"lowerBoundaryDistanceDegrees":"29.9","nearestBoundaryDistanceDegrees":"0.1"},"uncertainty":"The fixture reports geometric distance only; classification needs a separately supplied total angular uncertainty.","receiptSha256":"sha256:9f976302daccbd3b500c5ab916df748f1a627f9f8d007ff2b92b253f780a718f"},"path":"/knowledge/astrology/protocols/sign-boundary-distance"},{"slug":"interval-stability-sweep","category":"calculation-uncertainty","title":"Uncertain-time feature stability sweep","objective":"Evaluate a discrete label across the full allowed input interval rather than only at its midpoint.","requiredInputs":["Interval start","Interval end","Sampling/root policy","Requested derived label"],"orderedSteps":["Calculate both interval endpoints.","Search every internal boundary crossing.","Partition the interval at each crossing.","Report every attained label.","Withhold a scalar label when more than one occurs."],"outputs":["Attained-value set","Crossing list","Stable/unstable receipt"],"refusalConditions":["Only the midpoint is evaluated.","A detected crossing is dropped.","The interval is narrowed from chart preference."],"completionCriteria":["Every boundary is bracketed.","The value set is complete.","Unstable outputs are withheld."],"authorityIds":["calculation:historical-time-zone-uncertainty","calculation:house-cusp-boundaries","corporate:date-only-stability-audit"],"relatedAnswerSlugs":["what-to-do-when-birth-time-is-unknown","why-exact-time-matters"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:historical-time-zone-uncertainty","family":"calculation","title":"Historical timezone uncertainty","path":"/knowledge/astrology/calculations/historical-time-zone-uncertainty","establishes":"Historical civil time is reconstructed evidence, not a timeless mapping. A database rule can be precise while the underlying historical record remains uncertain.","boundary":"Modern software precision cannot recover information absent from the historical record.","status":"production-contract"},{"id":"calculation:house-cusp-boundaries","family":"calculation","title":"House-boundary sensitivity","path":"/knowledge/astrology/calculations/house-cusp-boundaries","establishes":"A house label is a discrete classification derived from a house system; its stability depends on the distance from relevant cusps and on input uncertainty.","boundary":"Selecting a preferred house from several candidates after seeing outcomes is post-hoc model selection.","status":"production-contract"},{"id":"corporate:date-only-stability-audit","family":"corporate","title":"Date-only corporate chart stability audit","path":"/knowledge/astrology/corporate-mundane/date-only-stability-audit","establishes":"Calculate at the representative midpoint and both interval edges, sample intermediate instants where necessary, compare ascendant, whole-sign houses, and pañcāṅga limbs, and publish only features stable across the declared window.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"interval-stability","inputs":{"startDegrees":"29.8","endDegrees":"30.2"},"units":{"startDegrees":"degrees","endDegrees":"degrees"},"assumptions":["The fixture interval is monotonic and does not wrap through 0°."],"outputs":{"startSignIndex":"0","endSignIndex":"1","stableSign":"false"},"uncertainty":"The differing endpoint sign indexes demonstrate instability; a production sweep must also search interior extrema and wraparound.","receiptSha256":"sha256:afcea28f3add0ee9847b409ec970b69df90727ecf72523d052b67e279f4fbadd"},"path":"/knowledge/astrology/protocols/interval-stability-sweep"},{"slug":"repeated-ingress-root-scan","category":"calculation-uncertainty","title":"Repeated-ingress root scan","objective":"Find every crossing of a declared longitude boundary, including retrograde recrossings.","requiredInputs":["Body and ephemeris","Time interval","Frame and boundary longitude","Search step and root tolerance"],"orderedSteps":["Sample the entire interval.","Unwrap longitude around the target.","Bracket every sign change.","Refine each bracket to tolerance.","Label direct or retrograde crossing and retain all roots."],"outputs":["Ordered ingress roots","Crossing directions","Search receipt"],"refusalConditions":["Only the first crossing is returned.","Frame or ayanāṁśa is implicit.","The search interval is chosen after observing an event."],"completionCriteria":["Every bracket is refined.","Repeated crossings remain distinct.","Search parameters are digest-bound."],"authorityIds":["timing:jupiter-ingress-reference","comparison:retrograde-repeated-crossings","calculation:retrograde-station-and-direct-motion"],"relatedAnswerSlugs":["what-is-a-planetary-ingress","why-an-ingress-can-happen-three-times"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"timing:jupiter-ingress-reference","family":"timing","title":"Jupiter ingress calculation reference","path":"/knowledge/astrology/timing/jupiter-ingress-reference","establishes":"A Jupiter ingress is a root of the signed angular distance between its declared geocentric ecliptic longitude and a selected 30-degree zodiac boundary. Jupiter commonly makes one or three crossings of a boundary depending on whether a retrograde loop straddles it.","boundary":"The crossing does not establish that a new life or business phase begins, that an event will occur, or that Jupiter causes an outcome.","status":"method-reference"},{"id":"comparison:retrograde-repeated-crossings","family":"comparison","title":"Retrograde motion and repeated boundary crossings","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/retrograde-repeated-crossings","establishes":"Stations and reversals describe the same planetary motion in both zodiac frames, although a station can fall inside differently named signs.","boundary":"Do not call the first, final, or closest crossing uniquely operative unless that selection policy was declared before the target outcome.","status":"parallel-unvalidated-models"},{"id":"calculation:retrograde-station-and-direct-motion","family":"calculation","title":"Retrograde, station, and direct-motion labels","path":"/knowledge/astrology/calculations/retrograde-station-and-direct-motion","establishes":"Retrograde and direct describe the sign of apparent longitudinal motion; stationary is a thresholded label around zero speed.","boundary":"Retrograde motion is apparent geometry and does not by itself imply delays, reversals, or outcomes.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"linear-ingress-root","inputs":{"startSeconds":"0","endSeconds":"3600","startDegrees":"29.8","endDegrees":"30.2","targetDegrees":"30"},"units":{"startSeconds":"seconds","endSeconds":"seconds","startDegrees":"degrees","endDegrees":"degrees","targetDegrees":"degrees","rootSeconds":"seconds"},"assumptions":["Linear interpolation is used only for this bracket fixture; production roots use the declared ephemeris solver."],"outputs":{"rootSeconds":"1800","method":"linear-bracket-fixture"},"uncertainty":"The fixture root is exact under linear interpolation; production uncertainty is bounded by ephemeris, sampling, and root tolerances.","receiptSha256":"sha256:8731ccebd91155a81e956b9b61eec02d7b26065832741bcb5025e94983c2bf73"},"path":"/knowledge/astrology/protocols/repeated-ingress-root-scan"},{"slug":"station-bracketing","category":"calculation-uncertainty","title":"Station bracketing and direction workflow","objective":"Locate a change in apparent longitudinal motion without equating a rounded daily value with a station.","requiredInputs":["Body","Apparent longitude function","Search interval","Derivative step","Root tolerance"],"orderedSteps":["Evaluate signed motion on a fixed grid.","Bracket every sign change.","Refine the zero of motion.","Classify direct-to-retrograde or reverse.","Retain near-zero uncertainty around the root."],"outputs":["Station instant set","Direction changes","Motion receipt"],"refusalConditions":["A rounded zero is accepted without a sign change.","One station is assumed per interval.","Geocentric and topocentric motion are mixed."],"completionCriteria":["Each root has an opposing-sign bracket.","Direction is explicit.","Tolerance and ephemeris are recorded."],"authorityIds":["timing:mercury-station-reference","calculation:retrograde-station-and-direct-motion","calculation:precision-rounding-and-uncertainty"],"relatedAnswerSlugs":["station-retrograde-and-direct-motion","why-an-ingress-can-happen-three-times"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"timing:mercury-station-reference","family":"timing","title":"Mercury direct and retrograde station reference","path":"/knowledge/astrology/timing/mercury-station-reference","establishes":"A Mercury station is the instant at which the time derivative of its unwrapped apparent geocentric ecliptic longitude changes sign. “Stationary” names a coordinate extremum; the body does not stop moving through physical space.","boundary":"A Mercury station does not establish that plans reverse, decisions fail, communications change, or any future event becomes more or less likely.","status":"method-reference"},{"id":"calculation:retrograde-station-and-direct-motion","family":"calculation","title":"Retrograde, station, and direct-motion labels","path":"/knowledge/astrology/calculations/retrograde-station-and-direct-motion","establishes":"Retrograde and direct describe the sign of apparent longitudinal motion; stationary is a thresholded label around zero speed.","boundary":"Retrograde motion is apparent geometry and does not by itself imply delays, reversals, or outcomes.","status":"production-contract"},{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"station-bracket","inputs":{"motionBeforeDegreesPerDay":"0.1","motionAfterDegreesPerDay":"-0.1"},"units":{"motionBeforeDegreesPerDay":"degrees/day","motionAfterDegreesPerDay":"degrees/day"},"assumptions":["The two samples straddle one continuous zero of apparent longitudinal motion."],"outputs":{"bracketed":"true","direction":"direct-to-retrograde"},"uncertainty":"The fixture proves a bracket and direction only; it does not estimate the station instant inside the bracket.","receiptSha256":"sha256:0c7adcaf8603595721dd1a333bc6086286479faabe0c11dafff5667291d51528"},"path":"/knowledge/astrology/protocols/station-bracketing"},{"slug":"lunation-phase-residual","category":"calculation-uncertainty","title":"Lunation phase-angle residual workflow","objective":"Solve a Moon–Sun longitude difference against a named phase target.","requiredInputs":["Sun longitude","Moon longitude","Target phase angle","Frame","Angular tolerance"],"orderedSteps":["Calculate both longitudes in one frame.","Form and normalize Moon minus Sun.","Compute the signed residual to the target.","Bracket and refine zero across time.","Keep eclipses outside this ordinary phase test."],"outputs":["Phase residual","At-target flag","Root receipt"],"refusalConditions":["Sun and Moon use different frames.","An eclipse is inferred from phase alone.","A rounded calendar label replaces the angular root."],"completionCriteria":["Residual recomputes.","Tolerance is explicit.","Eclipse eligibility remains a separate workflow."],"authorityIds":["timing:new-moon-reference","timing:full-moon-reference","calculation:tithi"],"relatedAnswerSlugs":["how-lunations-are-calculated","how-eclipse-times-are-established"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"timing:new-moon-reference","family":"timing","title":"New Moon calculation reference","path":"/knowledge/astrology/timing/new-moon-reference","establishes":"The New Moon is defined by a Sun–Moon phase-angle condition centered on 0°. A New Moon is not automatically a solar eclipse; eclipse geometry also requires suitable lunar latitude and observer alignment.","boundary":"The New Moon does not establish a beginning, culmination, crisis, release, or event outcome, and it is not evidence that a chart predicts reality.","status":"method-reference"},{"id":"timing:full-moon-reference","family":"timing","title":"Full Moon calculation reference","path":"/knowledge/astrology/timing/full-moon-reference","establishes":"The Full Moon is defined by a Sun–Moon phase-angle condition centered on 180°. A Full Moon is not automatically a lunar eclipse; most pass north or south of Earth’s shadow.","boundary":"The Full Moon does not establish a beginning, culmination, crisis, release, or event outcome, and it is not evidence that a chart predicts reality.","status":"method-reference"},{"id":"calculation:tithi","family":"calculation","title":"Tithi calculation","path":"/knowledge/astrology/calculations/tithi","establishes":"A tithi is one 12° interval of normalized geocentric Moon-minus-Sun ecliptic longitude, counted through waxing and waning halves.","boundary":"A calculated tithi does not establish that an activity is favorable.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"lunation-phase-residual","inputs":{"sunLongitudeDegrees":"10","moonLongitudeDegrees":"190","targetPhaseDegrees":"180","toleranceDegrees":"0.000001"},"units":{"sunLongitudeDegrees":"degrees","moonLongitudeDegrees":"degrees","targetPhaseDegrees":"degrees","toleranceDegrees":"degrees"},"assumptions":["All angles share one ecliptic frame and epoch."],"outputs":{"phaseResidualDegrees":"0","atTargetWithinTolerance":"true"},"uncertainty":"The zero residual is exact for the fixture values; event-time uncertainty requires a time-dependent ephemeris solve.","receiptSha256":"sha256:d1a0298f454f88c02787dc434fdbde4e26dd24c146ad989e0525c39e290355e8"},"path":"/knowledge/astrology/protocols/lunation-phase-residual"},{"slug":"vimshottari-balance-allocation","category":"calculation-uncertainty","title":"Vimśottarī opening-balance allocation","objective":"Calculate a tradition-relative remaining period from a declared lunar position and duration convention.","requiredInputs":["Natal lunar longitude","Named sidereal frame","Nakṣatra boundaries","Lord-year table","Duration basis"],"orderedSteps":["Derive the nakṣatra in the declared frame.","Compute elapsed fraction within it.","Select the tradition’s lord duration.","Allocate elapsed and remaining years.","Convert to dates only under one pinned duration basis."],"outputs":["Opening lord","Elapsed/remaining fraction","Balance receipt"],"refusalConditions":["Frame or ayanāṁśa is absent.","A duration basis changes between subperiods.","The result is described as a prediction."],"completionCriteria":["Fractions sum to one.","Elapsed plus remaining equals lord duration.","The tradition and arithmetic stay separately labelled."],"authorityIds":["timing:vimshottari-birth-balance-reference","timing:vimshottari-mahadasha-reference","calculation:nakshatra-and-pada"],"relatedAnswerSlugs":["how-vimshottari-dasha-starts","how-vimshottari-subperiods-are-calculated"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"timing:vimshottari-birth-balance-reference","family":"timing","title":"Vimśottarī birth balance calculation","path":"/knowledge/astrology/timing/vimshottari-birth-balance-reference","establishes":"The birth balance is the unexpired fraction of the mahādaśā ruled by the natal Moon’s nakṣatra. It anchors the entire reported 120-year chronology to the birth instant.","boundary":"A precise opening balance does not establish that the daśā system predicts events or that its conventional lords cause life outcomes.","status":"production-derived"},{"id":"timing:vimshottari-mahadasha-reference","family":"timing","title":"Vimśottarī mahādaśā sequence reference","path":"/knowledge/astrology/timing/vimshottari-mahadasha-reference","establishes":"A mahādaśā is a major interval in the fixed nine-lord Vimśottarī cycle. The conventional allocations total 120 nominal years before the sequence repeats.","boundary":"The mahādaśā sequence does not establish a causal timeline or demonstrate predictive skill merely because its dates are deterministic.","status":"production-derived"},{"id":"calculation:nakshatra-and-pada","family":"calculation","title":"Nakṣatra and pāda calculation","path":"/knowledge/astrology/calculations/nakshatra-and-pada","establishes":"The implemented nakṣatra grid contains 27 equal sectors of 13⅓°; each sector contains four pādas of 3⅓°.","boundary":"Nakṣatra assignment is a chart convention; personality and timing claims require separate sourced rules and empirical status.","status":"production-contract"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"vimshottari-balance","inputs":{"lordYears":"20","elapsedFraction":"0.25"},"units":{"lordYears":"years","remainingYears":"years","elapsedYears":"years"},"assumptions":["The lord duration and elapsed fraction are supplied fixtures; no natal chart or interpretive result is implied."],"outputs":{"remainingYears":"15","elapsedYears":"5"},"uncertainty":"Calendar dates inherit natal-time, lunar-position, boundary, and duration-basis uncertainty.","receiptSha256":"sha256:3cb19a8a35795d29e9acd46addb2fbf7351316b1a1132f78944d2923a3da5424"},"path":"/knowledge/astrology/protocols/vimshottari-balance-allocation"},{"slug":"combined-uncertainty-budget","category":"calculation-uncertainty","title":"Combined calculation-uncertainty budget","objective":"Keep independent uncertainty components visible and combine them only under a declared model.","requiredInputs":["Named uncertainty components","Common output unit","Dependence assumptions","Coverage policy"],"orderedSteps":["Convert components to one unit.","Separate bounded bias from standard uncertainty.","State whether components are independent.","Use root-sum-square only for independent standard components.","Compare the result with every relevant decision boundary."],"outputs":["Component table","Combined uncertainty","Boundary-stability decisions"],"refusalConditions":["Unlike units are combined.","Correlated terms are treated as independent.","Unknown uncertainty is entered as zero."],"completionCriteria":["Every component has provenance.","Combination assumptions are stated.","Unstable categorical outputs are withheld."],"authorityIds":["calculation:precision-rounding-and-uncertainty","calculation:reproducibility-digests","corporate:date-only-stability-audit"],"relatedAnswerSlugs":["sign-boundary-uncertainty","corporate-event-time-uncertainty"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"},{"id":"calculation:reproducibility-digests","family":"calculation","title":"Reproducibility digests and calculation provenance","path":"/knowledge/astrology/calculations/reproducibility-digests","establishes":"A digest is a cryptographic hash of canonical serialized data. It detects change but does not by itself prove that the data were true.","boundary":"A valid digest proves integrity relative to its hashed bytes, not scientific validity or authorship.","status":"production-contract"},{"id":"corporate:date-only-stability-audit","family":"corporate","title":"Date-only corporate chart stability audit","path":"/knowledge/astrology/corporate-mundane/date-only-stability-audit","establishes":"Calculate at the representative midpoint and both interval edges, sample intermediate instants where necessary, compare ascendant, whole-sign houses, and pañcāṅga limbs, and publish only features stable across the declared window.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":{"version":"astrology-calculation-receipt/1.0","operation":"root-sum-square-uncertainty","inputs":{"components":"0.02,0.03,0.01"},"units":{"components":"degrees","combinedStandardUncertainty":"degrees"},"assumptions":["The three components are independent standard uncertainties expressed in degrees."],"outputs":{"combinedStandardUncertainty":"0.037416574"},"uncertainty":"The receipt demonstrates the declared combination rule; correlated, bounded, or unknown components require a different model.","receiptSha256":"sha256:7ccaffff4a74b08fc443b5588e37f64e84d14fcfafc1cc5832c5b82c7dcf6823"},"path":"/knowledge/astrology/protocols/combined-uncertainty-budget"},{"slug":"preregister-one-testable-claim","category":"evaluation-falsifiability","title":"Preregister one falsifiable astrology claim","objective":"Translate an interpretive rule into one prospectively testable claim before outcomes are visible.","requiredInputs":["Frozen rule version","Eligible population","Observable outcome","Forecast horizon","Direction and threshold"],"orderedSteps":["State one claim in advance.","Define inclusion and exclusion without celestial features.","Choose one observable outcome and horizon.","Freeze the decision rule and abstention policy.","Digest and timestamp the registration before prediction."],"outputs":["Preregistered hypothesis","Eligibility contract","Registration digest"],"refusalConditions":["Outcome wording can change after observation.","Population selection uses chart favorability.","The claim has no possible disconfirming result."],"completionCriteria":["A null result is possible.","Timing precedes outcome availability.","All analytical choices are frozen."],"authorityIds":["corporate:corporate-outcome-preregistration","comparison:prospective-model-scoring","guide:corporate-charts"],"relatedAnswerSlugs":["how-astrology-could-be-tested","why-a-date-is-not-a-prediction"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"guide:corporate-charts","family":"guide","title":"Corporate charts: events, evidence, and uncertainty","path":"/knowledge/astrology/corporate-charts","establishes":"A company has no biological birth. Maha Celestial therefore charts a named organization event—such as filing acceptance or first commercial transaction—and preserves evidence for that event.","boundary":"A corporate chart cannot establish legal status, valuation, revenue, investment return, survival, or a guaranteed business outcome.","status":"public-method-guide"}],"fixture":null,"path":"/knowledge/astrology/protocols/preregister-one-testable-claim"},{"slug":"freeze-outcome-and-horizon","category":"evaluation-falsifiability","title":"Outcome definition and horizon lock","objective":"Make the scored event observable without substituting a nearby success after the deadline.","requiredInputs":["Outcome variable","Measurement source","Start and end instants","Availability timestamp","Missingness rule"],"orderedSteps":["Choose the outcome independently of predictions.","Define exactly when it counts.","Name the system of record.","Freeze the availability and missing-data policy.","Reject post-horizon outcome substitution."],"outputs":["Outcome contract","Observation schedule","Missingness policy"],"refusalConditions":["A proxy replaces a failed primary outcome.","The horizon moves after a miss.","Self-reported and instrumented outcomes are merged."],"completionCriteria":["One row has one decidable outcome.","Source and availability are auditable.","No chart field changes measurement."],"authorityIds":["corporate:corporate-outcome-preregistration","corporate:outcome-leakage-refusal-case-study","comparison:prospective-model-scoring"],"relatedAnswerSlugs":["how-astrology-could-be-tested","what-a-corporate-chart-cannot-establish"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:outcome-leakage-refusal-case-study","family":"corporate","title":"Sanitized case study: Outcome leakage causes forecast refusal","path":"/knowledge/astrology/corporate-mundane/outcome-leakage-refusal-case-study","establishes":"Compare registration, action, observation, and retrieval chronology; reject any forecast created after outcome availability; retain the example only as exploratory history.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"}],"fixture":null,"path":"/knowledge/astrology/protocols/freeze-outcome-and-horizon"},{"slug":"temporal-training-validation-test-split","category":"evaluation-falsifiability","title":"Temporal train–validation–test split","objective":"Prevent future outcomes from influencing fitting, model selection, or feature construction.","requiredInputs":["Chronological outcome corpus","Outcome availability time","Validation boundary","Test boundary","Feature version"],"orderedSteps":["Sort by when each outcome became available.","Fit only before the validation boundary.","Select allowed hyperparameters on validation only.","Lock the model before test begins.","Score test rows once without refitting."],"outputs":["Immutable split manifest","Locked model digest","Held-out score set"],"refusalConditions":["Random splitting leaks future information.","Test performance selects a model.","Feature definitions change during test."],"completionCriteria":["Every row belongs to exactly one split.","Training precedes validation and test.","Test remains untouched until lock."],"authorityIds":["comparison:prospective-model-scoring","corporate:ordinary-non-event-period-case-study","corporate:outcome-leakage-refusal-case-study"],"relatedAnswerSlugs":["how-astrology-could-be-tested","documented-tradition-versus-validated-claim"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:ordinary-non-event-period-case-study","family":"corporate","title":"Sanitized case study: Ordinary non-event periods in a corporate corpus","path":"/knowledge/astrology/corporate-mundane/ordinary-non-event-period-case-study","establishes":"Freeze a sampling clock, create candidate intervals independently of astrological features, require evidence-backed non-event records, and compile both classes through one state-vector schema.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:outcome-leakage-refusal-case-study","family":"corporate","title":"Sanitized case study: Outcome leakage causes forecast refusal","path":"/knowledge/astrology/corporate-mundane/outcome-leakage-refusal-case-study","establishes":"Compare registration, action, observation, and retrieval chronology; reject any forecast created after outcome availability; retain the example only as exploratory history.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/temporal-training-validation-test-split"},{"slug":"blind-prediction-and-outcome-join","category":"evaluation-falsifiability","title":"Blinded prediction and outcome join","objective":"Separate prediction production from outcome adjudication until both sides are immutable.","requiredInputs":["Pseudonymous task IDs","Locked predictions","Outcome records","Submission deadline","Join key"],"orderedSteps":["Generate task IDs without outcome labels.","Submit predictions before availability.","Seal prediction digests.","Adjudicate outcomes independently.","Join only by the frozen pseudonymous key."],"outputs":["Blinded task set","Submission receipts","Paired scoring table"],"refusalConditions":["Predictor sees outcome or proxy.","Outcome reviewer sees preferred model label.","Unmatched tasks are silently dropped."],"completionCriteria":["Every included prediction predates outcome.","Join cardinality is explicit.","Excluded rows retain reasons."],"authorityIds":["comparison:prospective-model-scoring","corporate:outcome-leakage-refusal-case-study","corporate:evidence-attachment-fingerprinting"],"relatedAnswerSlugs":["how-astrology-could-be-tested","documented-tradition-versus-validated-claim"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:outcome-leakage-refusal-case-study","family":"corporate","title":"Sanitized case study: Outcome leakage causes forecast refusal","path":"/knowledge/astrology/corporate-mundane/outcome-leakage-refusal-case-study","establishes":"Compare registration, action, observation, and retrieval chronology; reject any forecast created after outcome availability; retain the example only as exploratory history.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:evidence-attachment-fingerprinting","family":"corporate","title":"Evidence attachment fingerprinting without content retention","path":"/knowledge/astrology/corporate-mundane/evidence-attachment-fingerprinting","establishes":"Hash the attachment bytes in memory, validate media type and size limits, retain the SHA-256 digest and bounded metadata, and discard content unless a separate consent and retention policy authorizes storage.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/blind-prediction-and-outcome-join"},{"slug":"ordinary-baseline-comparison","category":"evaluation-falsifiability","title":"Ordinary-baseline comparison protocol","objective":"Require an astrology model to outperform a declared non-astrological comparator on identical tasks.","requiredInputs":["Locked astrology model","Ordinary baseline","Identical eligible tasks","Scoring rule","Minimum sample"],"orderedSteps":["Choose the baseline before outcomes.","Give both models identical non-outcome information.","Score all tasks including abstentions.","Calculate paired differences.","Report the baseline even when both models fail."],"outputs":["Paired score table","Coverage and abstention rates","Baseline comparison verdict"],"refusalConditions":["Only astrology successes are sampled.","The baseline gets less information.","The comparator is changed after scoring."],"completionCriteria":["Task sets are identical.","The comparison is prospective.","Uncertainty and null results are reported."],"authorityIds":["comparison:prospective-model-scoring","corporate:ordinary-non-event-period-case-study","corporate:corporate-outcome-preregistration"],"relatedAnswerSlugs":["how-astrology-could-be-tested","what-a-corporate-chart-cannot-establish"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:ordinary-non-event-period-case-study","family":"corporate","title":"Sanitized case study: Ordinary non-event periods in a corporate corpus","path":"/knowledge/astrology/corporate-mundane/ordinary-non-event-period-case-study","establishes":"Freeze a sampling clock, create candidate intervals independently of astrological features, require evidence-backed non-event records, and compile both classes through one state-vector schema.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/ordinary-baseline-comparison"},{"slug":"abstention-aware-scoring","category":"evaluation-falsifiability","title":"Abstention-aware forecast scoring","objective":"Prevent selective silence from inflating apparent accuracy.","requiredInputs":["All eligible tasks","Prediction or abstention per task","Locked scoring rule","Coverage threshold"],"orderedSteps":["Require one submission state for every task.","Count abstention in coverage.","Score accuracy both overall and when answered.","Apply the preregistered abstention penalty.","Report confidence intervals and missingness."],"outputs":["Coverage","Overall score","Conditional score","Abstention count"],"refusalConditions":["Abstained tasks vanish.","Coverage threshold changes after scoring.","Only correct answered tasks are reported."],"completionCriteria":["Tasks equal answered plus abstained.","Coverage accompanies accuracy.","Policy matches preregistration."],"authorityIds":["comparison:prospective-model-scoring","corporate:corporate-outcome-preregistration","corporate:ordinary-non-event-period-case-study"],"relatedAnswerSlugs":["how-astrology-could-be-tested","documented-tradition-versus-validated-claim"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:ordinary-non-event-period-case-study","family":"corporate","title":"Sanitized case study: Ordinary non-event periods in a corporate corpus","path":"/knowledge/astrology/corporate-mundane/ordinary-non-event-period-case-study","establishes":"Freeze a sampling clock, create candidate intervals independently of astrological features, require evidence-backed non-event records, and compile both classes through one state-vector schema.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/abstention-aware-scoring"},{"slug":"multiplicity-and-stopping-rule","category":"evaluation-falsifiability","title":"Multiplicity and stopping-rule protocol","objective":"Prevent many attempted claims or repeated peeking from manufacturing a positive result.","requiredInputs":["Hypothesis family","Primary comparison","Adjustment method","Fixed or sequential stopping rule","Maximum sample"],"orderedSteps":["Enumerate every planned test.","Designate the primary test.","Freeze multiplicity adjustment.","Freeze when data collection stops.","Report all tests and looks."],"outputs":["Hypothesis-family manifest","Adjusted results","Stopping audit"],"refusalConditions":["Only the best frame is reported.","Data collection stops after a favorable look.","Exploratory tests are called confirmatory."],"completionCriteria":["Every planned test is accounted for.","Adjustment is reproducible.","Stopping follows the locked rule."],"authorityIds":["comparison:prospective-model-scoring","corporate:corporate-outcome-preregistration"],"relatedAnswerSlugs":["how-astrology-could-be-tested","tropical-versus-sidereal-zodiac"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/multiplicity-and-stopping-rule"},{"slug":"null-adverse-and-replication-reporting","category":"evaluation-falsifiability","title":"Null, adverse, and replication reporting","objective":"Publish the complete evidentiary outcome rather than only favorable forecasts.","requiredInputs":["Registered hypothesis","Locked analysis","All eligible outcomes","Protocol deviations","Replication status"],"orderedSteps":["Verify the registration and data digest.","Run the locked analysis once.","Classify positive, null, inconclusive, or adverse.","Publish deviations and missingness.","Keep replication distinct from discovery."],"outputs":["Complete result report","Deviation log","Replication requirement"],"refusalConditions":["A null result is omitted.","An adverse result is relabelled exploratory.","A same-dataset rerun is called replication."],"completionCriteria":["All outcomes reconcile.","Classification follows the locked policy.","Claims do not exceed the observed protocol."],"authorityIds":["comparison:prospective-model-scoring","corporate:corporate-outcome-preregistration","corporate:outcome-leakage-refusal-case-study"],"relatedAnswerSlugs":["documented-tradition-versus-validated-claim","how-astrology-could-be-tested"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"},{"id":"corporate:corporate-outcome-preregistration","family":"corporate","title":"Preregistering corporate timing outcomes","path":"/knowledge/astrology/corporate-mundane/corporate-outcome-preregistration","establishes":"Freeze event eligibility, planetary features, model version, prediction, KPI, system of record, outcome horizon, random or ordinary baseline, exclusions, and analysis plan before the action begins.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"},{"id":"corporate:outcome-leakage-refusal-case-study","family":"corporate","title":"Sanitized case study: Outcome leakage causes forecast refusal","path":"/knowledge/astrology/corporate-mundane/outcome-leakage-refusal-case-study","establishes":"Compare registration, action, observation, and retrieval chronology; reject any forecast created after outcome availability; retain the example only as exploratory history.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/null-adverse-and-replication-reporting"},{"slug":"tropical-sidereal-decision-map","category":"tradition-comparison","title":"Tropical–sidereal comparison decision map","objective":"Decide whether two chart statements are coordinate comparisons, tradition comparisons, or invalid blends.","requiredInputs":["Shared celestial state","Tropical convention","Named sidereal convention","Rule namespace","Comparison question"],"orderedSteps":["Verify the shared body and instant.","Separate coordinate transformation from interpretation.","Compare numerical longitude before sign labels.","Apply each tradition’s own rule namespace.","Refuse a winner without prospective evaluation."],"outputs":["Shared-fact table","Frame-specific outputs","Allowed and prohibited comparisons"],"refusalConditions":["Sidereal convention is unnamed.","Rules cross namespaces.","A sign disagreement is called different sky."],"completionCriteria":["Agreement and disagreement are both explicit.","No blended chart is emitted.","Empirical status remains separate."],"authorityIds":["comparison:zodiac-zero-points","comparison:longitude-and-sign-labels","calculation:sidereal-zodiac-longitude"],"relatedAnswerSlugs":["tropical-versus-sidereal-zodiac","how-to-compare-astrology-traditions"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:zodiac-zero-points","family":"comparison","title":"Zodiac zero points: equinox and Lahiri reference","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/zodiac-zero-points","establishes":"The body, instant, observer assumptions, and underlying ecliptic direction are unchanged. The comparison begins from one retained tropical longitude rather than calculating two unrelated skies.","boundary":"Do not average the longitudes, call Lahiri “the sidereal zodiac,” or select a zero point after reading an interpretation or outcome.","status":"parallel-unvalidated-models"},{"id":"comparison:longitude-and-sign-labels","family":"comparison","title":"One celestial direction, two sign labels","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/longitude-and-sign-labels","establishes":"Physical state vectors, apparent direction, direct or retrograde motion, and angular relationships remain facts about the same calculated moment.","boundary":"Do not describe a planet as simultaneously occupying an unlabeled hybrid sign or choose whichever sign yields the more compelling narrative.","status":"parallel-unvalidated-models"},{"id":"calculation:sidereal-zodiac-longitude","family":"calculation","title":"Sidereal zodiac longitude","path":"/knowledge/astrology/calculations/sidereal-zodiac-longitude","establishes":"Sidereal zodiac longitude is a tropical ecliptic longitude transformed by a selected stellar-reference offset called an ayanāṁśa.","boundary":"A sidereal conversion does not show that one astrological system is empirically superior.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/tropical-sidereal-decision-map"},{"slug":"geocentric-topocentric-decision-map","category":"tradition-comparison","title":"Geocentric–topocentric decision map","objective":"Choose or compare origins from the observable and declared method, not from the desired result.","requiredInputs":["Requested observable","Body distance relevance","Observer contract","Method namespace"],"orderedSteps":["Ask whether the output is Earth-center or local.","Require observer data for local geometry.","Compute parallel outputs under shared dependencies when comparing.","Quantify the difference.","Keep interpretive rules bound to their declared origin."],"outputs":["Origin decision","Parallel-coordinate delta","Rule eligibility map"],"refusalConditions":["Observer data are missing.","Origins are averaged.","A preferred interpretation chooses the origin."],"completionCriteria":["The choice follows the observable.","Both outputs are labelled.","Rule eligibility is explicit."],"authorityIds":["calculation:geocentric-vs-topocentric","calculation:observer-latitude-longitude","calculation:elevation-and-horizon"],"relatedAnswerSlugs":["topocentric-versus-geocentric-chart","how-to-compare-astrology-traditions"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:geocentric-vs-topocentric","family":"calculation","title":"Geocentric versus topocentric positions","path":"/knowledge/astrology/calculations/geocentric-vs-topocentric","establishes":"Geocentric coordinates use Earth’s center as origin; topocentric coordinates use a specified observing site on or near Earth’s surface.","boundary":"Topocentric output is not intrinsically more appropriate for every astrological tradition.","status":"production-contract"},{"id":"calculation:observer-latitude-longitude","family":"calculation","title":"Observer latitude and longitude","path":"/knowledge/astrology/calculations/observer-latitude-longitude","establishes":"Observer coordinates locate the calculation origin on Earth. Longitude sets local rotation angle; latitude sets the horizon orientation.","boundary":"A geocoder result does not prove the person or event was physically at that point.","status":"production-contract"},{"id":"calculation:elevation-and-horizon","family":"calculation","title":"Elevation, horizon, and rise/set calculations","path":"/knowledge/astrology/calculations/elevation-and-horizon","establishes":"Elevation changes the observer position and visible horizon. Atmospheric refraction and terrain obstruction are separate corrections.","boundary":"A computed standard sunrise is not necessarily the first locally visible light over terrain.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/geocentric-topocentric-decision-map"},{"slug":"mean-true-node-decision-map","category":"tradition-comparison","title":"Mean–true lunar-node decision map","objective":"Preserve two computational definitions and prevent silent substitution in rule application.","requiredInputs":["Shared instant","Mean-node algorithm","True-node algorithm","Tradition rule namespace","Boundary tolerance"],"orderedSteps":["Calculate both nodes under named algorithms.","Retain the nodal-axis relation.","Measure longitude and sign differences.","Apply only rules declaring the consumed node.","Evaluate models prospectively if performance is compared."],"outputs":["Parallel node positions","Difference report","Rule eligibility map"],"refusalConditions":["The node type is absent.","One value overwrites the other.","Retrospective fit selects a node."],"completionCriteria":["Algorithms are versioned.","Every rule names mean or true.","No empirical winner is inferred."],"authorityIds":["calculation:mean-vs-true-lunar-node","calculation:precision-rounding-and-uncertainty","comparison:prospective-model-scoring"],"relatedAnswerSlugs":["mean-versus-true-lunar-node","how-to-compare-astrology-traditions"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"calculation:mean-vs-true-lunar-node","family":"calculation","title":"Mean versus true lunar node","path":"/knowledge/astrology/calculations/mean-vs-true-lunar-node","establishes":"The mean node follows a smoothed precessing orbit-plane model; the true node adds periodic oscillation from the instantaneous lunar orbit model.","boundary":"Neither node model has demonstrated predictive superiority in Maha’s current evidence corpus.","status":"production-contract"},{"id":"calculation:precision-rounding-and-uncertainty","family":"calculation","title":"Numerical precision, rounding, and uncertainty","path":"/knowledge/astrology/calculations/precision-rounding-and-uncertainty","establishes":"Precision describes representation; uncertainty bounds plausible error from inputs, models, data, and transformations. They are not interchangeable.","boundary":"More decimal places do not imply better source evidence or predictive performance.","status":"production-contract"},{"id":"comparison:prospective-model-scoring","family":"comparison","title":"Prospective scoring without post-hoc frame selection","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/prospective-model-scoring","establishes":"Every model receives the same eligible tasks, outcome definitions, information cutoff, scoring rule, blinded evaluation schedule, and prospectively fixed stopping point.","boundary":"Do not report the better retrospective score as the prospective policy, drop discordant tasks, tune weights on the test set, or call agreement proof of truth.","status":"parallel-unvalidated-models"}],"fixture":null,"path":"/knowledge/astrology/protocols/mean-true-node-decision-map"},{"slug":"house-system-decision-map","category":"tradition-comparison","title":"House-system comparison decision map","objective":"Compare whole-sign, equal, and quadrant houses without merging incompatible definitions.","requiredInputs":["Verified instant and observer","Ascendant and midheaven","Named house systems","Polar eligibility","Rule namespaces"],"orderedSteps":["Establish shared angular geometry.","Calculate each system independently.","Check system-specific latitude limits.","Compare house assignments as parallel outputs.","Apply only rules authored for each system."],"outputs":["House cusps by system","Assignment differences","Eligibility and refusal map"],"refusalConditions":["Unknown time is supplied.","Systems are combined into consensus houses.","A system is selected by preferred reading."],"completionCriteria":["Each cusp set is complete or refused.","Differences remain visible.","Rules do not cross namespaces."],"authorityIds":["comparison:ascendant-and-whole-sign-houses","calculation:whole-sign-houses","calculation:placidus-houses","calculation:polar-house-limitations"],"relatedAnswerSlugs":["why-house-systems-disagree","ascendant-and-whole-sign-houses"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"comparison:ascendant-and-whole-sign-houses","family":"comparison","title":"Ascendant labels and whole-sign house geometry","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/ascendant-and-whole-sign-houses","establishes":"The eastern intersection of the ecliptic and local horizon is one geometric direction for the declared instant, observer, and Earth-orientation convention.","boundary":"Do not combine a tropical ascendant with sidereal planetary signs or borrow house rulers across frames unless an explicitly named tradition rule requires that combination.","status":"parallel-unvalidated-models"},{"id":"calculation:whole-sign-houses","family":"calculation","title":"Whole-sign house assignment","path":"/knowledge/astrology/calculations/whole-sign-houses","establishes":"Whole-sign houses divide the zodiac into twelve sign sectors; the sign containing the ascendant becomes the first house regardless of ascendant degree.","boundary":"Whole-sign simplicity does not prove the associated house interpretations.","status":"production-contract"},{"id":"calculation:placidus-houses","family":"calculation","title":"Placidus house convention","path":"/knowledge/astrology/calculations/placidus-houses","establishes":"Placidus is a time-proportional quadrant system whose intermediate cusps are derived from diurnal motion between angular positions.","boundary":"Placidus and whole-sign charts must be evaluated as separate declared models, not averaged.","status":"comparison-only"},{"id":"calculation:polar-house-limitations","family":"calculation","title":"Polar latitude limitations in house calculation","path":"/knowledge/astrology/calculations/polar-house-limitations","establishes":"High-latitude geometry can remove daily rise/set events and make specific time-division house equations undefined, while the ecliptic and horizon still intersect.","boundary":"Polar exceptions do not justify inventing an event time or forcing an auspiciousness score.","status":"production-contract"}],"fixture":null,"path":"/knowledge/astrology/protocols/house-system-decision-map"},{"slug":"hellenistic-jyotisha-decision-map","category":"tradition-comparison","title":"Hellenistic–Jyotiṣa decision map","objective":"Compare documented systems by source, frame, chart type, and rule semantics without manufacturing a hybrid.","requiredInputs":["Named traditions and versions","Rights-cleared source passages","Coordinate-frame declarations","Technique names","Comparison axis"],"orderedSteps":["Verify that both traditions have evidence for the technique.","Separate shared geometry from rule semantics.","Map similar terms without declaring identity.","Record agreements and disagreements symmetrically.","Require prospective testing for performance claims."],"outputs":["Typed correspondence map","Unsupported-equivalence list","Evaluation requirements"],"refusalConditions":["A technique exists on only one side.","Translation similarity becomes historical identity.","One tradition’s rule fills the other’s gap."],"completionCriteria":["Every correspondence cites both sides.","Missing evidence remains missing.","No blended rule is emitted."],"authorityIds":["tradition:hellenistic-ptolemaic","tradition:vedic-jyotisha","comparison:dignity-rulership-and-house-lords"],"relatedAnswerSlugs":["how-to-compare-astrology-traditions","documented-tradition-versus-validated-claim"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"tradition:hellenistic-ptolemaic","family":"tradition","title":"Hellenistic (Ptolemaic)","path":"/knowledge/astrology/hellenistic-ptolemaic","establishes":"The system set out in Ptolemy’s Tetrabiblos, which grounds planetary signification in the four elemental qualities and treats the zodiac as measured from the equinox. It is the transmission route for much later Western practice, and it is not identical to any of them.","boundary":"The registry documents a named interpretive tradition. It does not claim that any rule predicts an outcome.","status":"documented-unvalidated-tradition"},{"id":"tradition:vedic-jyotisha","family":"tradition","title":"Vedic (Jyotiṣa)","path":"/knowledge/astrology/vedic-jyotisha","establishes":"The Indian sidereal system represented here by a deliberately small source-bound corpus. Its calendrical arithmetic is reproducible; every newly encoded natal, timing, mundane, or corporate interpretation remains withheld until passage fidelity and rule formalization receive scoped practitioner review.","boundary":"The registry documents a named interpretive tradition. It does not claim that any rule predicts an outcome.","status":"documented-unvalidated-tradition"},{"id":"comparison:dignity-rulership-and-house-lords","family":"comparison","title":"Dignity, rulership, and house-lord disagreements","path":"/knowledge/astrology/tropical-vs-sidereal/comparisons/dignity-rulership-and-house-lords","establishes":"The celestial bodies and their geometric directions are unchanged; dignity and rulership are symbolic classifications supplied by a named tradition.","boundary":"Do not choose the stronger dignity, combine two rulers into an unlabeled result, or treat agreement as independent empirical confirmation.","status":"parallel-unvalidated-models"}],"fixture":null,"path":"/knowledge/astrology/protocols/hellenistic-jyotisha-decision-map"},{"slug":"natal-horary-mundane-scope-map","category":"tradition-comparison","title":"Natal–horary–mundane scope decision map","objective":"Choose the chart class from the question and event evidence before any rules are applied.","requiredInputs":["Question type","Subject identity","Candidate event records","Named tradition","Available rule corpus"],"orderedSteps":["Classify birth, understood-question, or public-event scope.","Verify the corresponding event evidence.","Check whether the tradition has reviewed rules for that chart class.","Refuse rules imported from another class.","Keep unpopulated traditions visibly unpopulated."],"outputs":["Chart-class decision","Eligible rule set","Withheld-rule reasons"],"refusalConditions":["A birth rule is applied to incorporation.","Horary rules are reconstructed from OCR.","A public event is selected from outcome fit."],"completionCriteria":["One class is selected before calculation.","Rule provenance matches the class.","Withheld corpora remain withheld."],"authorityIds":["tradition:hellenistic-ptolemaic","tradition:horary-lilly","corporate:organization-event-taxonomy"],"relatedAnswerSlugs":["what-ptolemaic-astrology-means-here","why-horary-rules-are-withheld","which-event-starts-a-corporate-chart"],"boundary":"This protocol can establish reproducibility, declared scope, or prospective test status. It cannot turn astrological interpretation into an astronomical fact or claim predictive validity without the separately specified evaluation result.","authority":[{"id":"tradition:hellenistic-ptolemaic","family":"tradition","title":"Hellenistic (Ptolemaic)","path":"/knowledge/astrology/hellenistic-ptolemaic","establishes":"The system set out in Ptolemy’s Tetrabiblos, which grounds planetary signification in the four elemental qualities and treats the zodiac as measured from the equinox. It is the transmission route for much later Western practice, and it is not identical to any of them.","boundary":"The registry documents a named interpretive tradition. It does not claim that any rule predicts an outcome.","status":"documented-unvalidated-tradition"},{"id":"tradition:horary-lilly","family":"tradition","title":"Horary (Lilly)","path":"/knowledge/astrology/horary-lilly","establishes":"The question-based practice codified in William Lilly’s Christian Astrology, which judges a chart cast for the moment a question is understood rather than for a birth.","boundary":"No rights-cleared, proofread transcription of the 1647 text is available. The source is public domain, but every machine transcription found is unproofread OCR; publishing rules from it would violate this layer’s transcription-fidelity claim.","status":"registered-rules-withheld"},{"id":"corporate:organization-event-taxonomy","family":"corporate","title":"Organization-event taxonomy for corporate charts","path":"/knowledge/astrology/corporate-mundane/organization-event-taxonomy","establishes":"Name the event before calculation, select one supported event type, preserve competing candidates, and prohibit retroactive substitution based on which chart looks more favorable. Each interpretation rule must declare the event types it can consume.","boundary":"The method does not establish valuation, investment return, legal status, revenue, survival, market adoption, or a guaranteed business outcome, and it is not evidence that astrology predicts organizational events.","status":"not-evidence-of-predictive-skill"}],"fixture":null,"path":"/knowledge/astrology/protocols/natal-horary-mundane-scope-map"}],"answerGraph":"/knowledge/astrology/questions","cohortDigest":"sha256:d3626d335619d87bb7492181e7cfadcc59e39071b009bbf7f9acd3c5fa2ead81","predictiveValidityClaimed":false}