Product status · verified 30 July 2026

What is built.
What you can use.

REACHABLE ACCESS15 / 32All limited access — nothing is on general public availability yet
NOT AVAILABLE10 / 32Blocked, or with no announced access
BUILD STATES8Distinct declared delivery states in use
LAST VERIFIED30 July 2026Against source repositories, not a status feed
01Two independent states

Built is not the same as available.

A capability can be fully implemented and still unavailable, or authored in full and not yet running. Separating the two is the only way a status page stays honest.

DELIVERYHow far it is built

Operational core9
A current end-to-end data path has been verified for the capability's stated scope.
Implemented6
Substantial code or interface exists, although every surrounding workflow may not yet be complete.
Authored6
The editorial or curriculum corpus exists and can be inspected independently of runtime availability.
Expanding2
A verified core exists while named categories, routes or supporting operations are still being deepened.
In verification2
Implementation exists, but a contract, correctness, security or end-to-end issue prevents an operational claim.
Designed3
A detailed product or pedagogical specification exists without a fully verified operation.
Planned3
The capability belongs to the approved roadmap but is not a current product operation.
Externally pending1
The state depends on a publisher, accreditor, commercial approval or other external decision.

AVAILABILITYWhether you can use it

Public0
A visitor can use or obtain the capability through a verified public path.
Limited access15
The capability exists for a controlled, pre-launch, invited or otherwise bounded audience.
Internal7
The capability is available only inside AstroCorp operations or product development.
Blocked3
A known defect or dependency currently prevents normal availability.
Unannounced7
No public availability, price, publication date or release commitment has been approved.
02The complete register

Every capability, including the awkward ones.

Filter by availability. Nothing is hidden behind a filter — the counts above and the rows below come from the same record.

Professional practice

  • Accounts and authorizationCore implemented

    Operational coreLimited access

    BOUNDARYDo not imply that every service has identical authorization behavior.

  • Client recordsCore implemented

    Operational coreLimited access

    BOUNDARYSurrounding follow-up and booking operations remain separate states.

  • Charts and divisionalsCore implemented

    Operational coreLimited access

    BOUNDARYName only verified chart and ayanamsha coverage.

  • Dasha systemsCore implemented

    Operational coreLimited access

    BOUNDARYTiming is evidence for judgment, not deterministic certainty.

Named methods

  • KP astrologyCore implemented

    Operational coreLimited access

    BOUNDARYKeep KP's method distinct from Parashari reasoning.

  • JaiminiImplemented coverage

    ImplementedLimited access

    BOUNDARYVerify individual calculations before publishing granular coverage claims.

  • NadiAuthored and in development

    AuthoredInternal

    BOUNDARYNever imply one universal Nadi method.

  • Tajika and VarshaphalaImplemented coverage

    ImplementedLimited access

    BOUNDARYGranular production calculations require route-level verification.

  • Lal KitabImplemented coverage

    ImplementedLimited access

    BOUNDARYDo not imply a separately verified service.

  • PrashnaAuthored advanced study

    AuthoredInternal

    BOUNDARYNot a complete standalone production workflow.

Instruments

  • PanchangaCore implemented

    Operational coreLimited access

    BOUNDARYDescribe location-sensitive calculations; never imply universal local equivalence.

  • Muhurta engineCore implemented · expanding

    ExpandingLimited access

    BOUNDARYName verified event categories instead of claiming every event type.

  • Compatibility evidenceCore implemented · expanding

    ExpandingLimited access

    BOUNDARYPresent evidence and human counsel, not a fabricated universal score.

  • Chaldean numerology168-endpoint core implemented

    Operational coreLimited access

    BOUNDARYKeep Chaldean distinct from Vedic numerology and Lo Shu.

  • Vedic numerologyPlanned

    PlannedUnannounced

    BOUNDARYDo not describe it as a current calculation service.

  • Lo Shu gridPlanned

    PlannedUnannounced

    BOUNDARYDo not describe it as a current calculation service.

Solutions

  • Vastu suiteAuthored system · implemented interface

    ImplementedLimited access

    BOUNDARYDo not claim a complete calculation service until it passes verification.

  • Report suiteProduct system in development

    DesignedInternal

    BOUNDARYDo not imply standalone automated report generation is publicly available.

Learning

  • Tier One curriculum598 lessons authored · runtime implemented

    Operational coreLimited access

    BOUNDARYAvailability remains bounded until the public access path is verified.

  • Tier Two curriculum594 lessons authored

    AuthoredBlocked

    BOUNDARYDirectory drift currently prevents a normal runtime-availability claim.

  • Learning interactives565 implemented interactives

    ImplementedLimited access

    BOUNDARYImplemented is not the same as production-verified.

  • Assessment banks1,193 assessment banks authored

    AuthoredBlocked

    BOUNDARYDo not claim examination-grade integrity until answer exposure is corrected.

  • Mastery and progressIn verification

    In verificationBlocked

    BOUNDARYGateway and correctness gaps prevent a continuous-operation claim.

  • AI ProfessorDesigned learning system

    DesignedInternal

    BOUNDARYDo not call it a fully operational autonomous professor.

  • Certification and capstoneCapstone designed · certification unannounced

    DesignedUnannounced

    BOUNDARYDo not promise an available certification.

Books

  • Book One manuscriptComplete editorial manuscript

    AuthoredUnannounced

    BOUNDARYNot a published retail book; price, ISBN and release date are unannounced.

  • Book Two manuscriptManuscript in development

    AuthoredInternal

    BOUNDARYWorking proof and drafted chapters are not a finished publication.

Product infrastructure

  • API gatewayOperational infrastructure

    Operational coreInternal

    BOUNDARYDo not claim enterprise security until access boundaries pass verification.

  • Enterprise API accessEnterprise access in preparation

    In verificationUnannounced

    BOUNDARYNo standardized purchasable plan or public security claim is approved.

  • Administration surfacesInternal operations

    ImplementedInternal

    BOUNDARYNever expose sensitive operating detail as public product proof.

Company and commercial

  • AccreditationNot currently accredited

    Externally pendingUnannounced

    BOUNDARYNever imply held or guaranteed future accreditation.

  • Access plans and pricingAccess plans unannounced

    PlannedUnannounced

    BOUNDARYDo not publish invented prices, dates or inclusions.

03Verification record

Numbers, and where each one came from.

These are counted from source repositories on the date shown, not reported by a live telemetry feed. Any of them can be recounted independently.

Authored lessons1,192Filesystem count of Tier One and Tier Two lesson files
Curriculum modules4824 module directories in each tier
Assessment-bank records1,193JSON files under the assessment bank
Interactive specifications972Files directly under the interactive-specs directory
Chaldean endpoint surface168Raw calculator slugs plus service routes and health

WHAT THIS PAGE IS NOTThis is not an uptime dashboard and does not report live service health. It is a dated statement of build and availability state, republished when a state changes. A dated product changelog will appear here once material product changes are recorded at source; inventing entries now would make this page exactly the kind of marketing it exists to avoid. The company and engine behind these states are recorded on theGrahvani and AstroCorp page.