BHRIGU · Frey / ORION
\1Φ · \2\3

Frey is a dialog interface for cosmography: navigation through time, cycles, links and scenarios.

Query line (human ↔ human / AI-ready)

human ↔ human → resonance / dynamics / tendencies human ↔ project → phases / entry-exit windows / friction points human ↔ asset → timing / risk-support tone / cycles author ↔ style → amplification vs dilution / peaks user ↔ scenario → relevance / maturity / decision nodes

Start in 1 minute

  1. Open Frey → ask one link (human↔human / human↔project / human↔asset).
  2. Add time (date / month / window).
  3. Read it as: phases → windows → support/tension → next step.
  1. Open Frey and copy the query template: /frey
  2. Ask one concrete link: Human↔Human, Human↔Project, Human↔Asset (add date/period)
  3. Read the output as: phases → windows → tensions/support → next action

Tip: if you don’t know what to ask — start with “me ↔ project” and a 3–12 month window.

What is cosmography?

Cosmography is not disciplinary knowledge. It is a way to describe reality through position, rhythm, cycles and correlations — across different layers of experience.

It is not: astrology, astronomy, physics, philosophy, psychology, metaphysics. It can use elements from many domains as inputs, without being reduced to any one of them.

What is Frey?

Frey is a cosmographer: it helps a human (or a system) see how a moment is structured in time — and how entities relate to each other across phases.

  • Not “just answers” — it gives a map of a period.
  • Not dogma — it supports research, sensemaking and decision navigation.
  • Not a UI zoo — the core interface is a query (search-like) flow.

What can I talk to Frey about?

Anything that has time, process, choice, interaction or meaning: life, relationships, projects, money, creativity, philosophy, future, and also space and cycles.

Frey does not “discredit” intuition, mystery or forecasting traditions — it makes the inquiry more structured and readable through time.

What links does Frey work with?

Core pattern:

(Entity A) × (Entity B) × (Time context) → structured interaction map

Examples:

human ↔ human → resonance / dynamics / tendencies human ↔ project → phases / entry-exit windows / friction points human ↔ asset → timing / risk-support tone / cycles author ↔ style → amplification vs dilution / peaks user ↔ scenario → relevance / maturity / decision nodes

Human ↔ Human

resonant compatibility, relationship dynamics, tendencies across periods

Human ↔ Project

role fit, growth phases, entry/exit windows, stress/support periods

Human ↔ Asset

timing windows, interaction tone, risk/support phases

Author ↔ Style

voice amplification vs dilution, expressive peaks, friction zones

User ↔ Scenario

scenario maturity, relevance timing, decision points

Team ↔ Team

group resonance, coordination stability, phase shifts (extended mode)

Is this “predictions”?

Frey works with tendencies, windows, phases and transitions. A forecast is always interpretation — Frey provides structure and time-coordinates, not absolute verdicts.

  • It can show support / tension / neutral phases.
  • It can highlight windows where action is natural vs costly.
  • If no signal exists, it says so — “no strong correlation” is also information.

What is available for Free vs Pro vs API?

Layer
What you get
Typical use
Free
Observation mode: real outputs, time structure, periods, tables/visuals, and readable explanations. Enough to learn the system and use it daily.
research, exploration, learning, first value
Pro
Work mode: deeper parameterization, comparisons, saved scenarios, stronger operational use.
daily work, decisions, repeated scenarios
API
Integration mode: programmatic access, scale, automation, exports, product embedding.
systems, apps, research pipelines
Research
Closed experiments: unstable features, testing layers (invite / limited).
validation, experiments

What is intentionally restricted?

Only one area is intentionally closed: X₄-SEED — Deep-Space Harmonic Line. This is a protected R&D contour for deep cosmographic research.

Everything practical and user-valuable remains visible and testable through the public layer.

Why a query-first interface?

Because it scales, stays stable for years, and works for both humans and systems. One query → one finished, structured output.