103 lines
3.4 KiB
Markdown
103 lines
3.4 KiB
Markdown
# EDUT Public-Facing System Vision
|
|
|
|
## Core Intent
|
|
|
|
`edut.ai` is the public face of EDUT and mirrors the product architecture:
|
|
|
|
1. Human layer: emotional signal and deliberate minimalism.
|
|
2. Math layer: deterministic metadata and machine-readable structure.
|
|
3. AI layer: high-context abstract for AI systems and accessibility.
|
|
|
|
The site should feel precise and established while avoiding disclosure of private implementation IP.
|
|
|
|
## Primary Experience (Two-Factor Designation)
|
|
|
|
1. A visitor lands on `edut.ai`.
|
|
2. They see only the globe, identity line, and meaning line.
|
|
3. They click anywhere.
|
|
4. A minimal phone field appears inline (same aesthetic language).
|
|
5. They enter their number and submit.
|
|
6. They receive SMS from Edut protocol channel with designation token and `CONFIRM` instruction.
|
|
7. They reply `CONFIRM`.
|
|
8. Once phone verification is detected, the page opens the classified mailto request for the same designation code.
|
|
9. They send the email.
|
|
10. They receive confirmation showing designation + auth token with both channels verified.
|
|
|
|
The interaction is intended to feel like protocol registration, not a marketing funnel.
|
|
|
|
## Three-Layer Web Model
|
|
|
|
### 1) Human Layer
|
|
|
|
- Brand identity: `edut · עֵדוּת` (never translated).
|
|
- Minimal visual language with no cluttered CTA stack.
|
|
- Emotional tone: witness, evidence, governance.
|
|
|
|
### 2) Math Layer
|
|
|
|
- Open Graph metadata for deterministic categorization.
|
|
- Schema.org organization metadata.
|
|
- Stable semantic structure for indexing and portability.
|
|
|
|
### 3) AI + Accessibility Layer
|
|
|
|
- Full research abstract in DOM.
|
|
- Visually hidden but available to screen readers.
|
|
- Localized via language bundles for regional AI interpretation.
|
|
- Ready for future read-aloud/listen mode.
|
|
|
|
## Infrastructure Targets
|
|
|
|
- `edut.ai`: primary public surface and business identity.
|
|
- `edut.dev`: developer-facing domain (same landing for now).
|
|
- `secret.edut.ai`: inbound designation email namespace.
|
|
- `api.edut.ai`: API and webhook endpoint (`/secret/*`, `/twilio/inbound`, `/mailgun/inbound`).
|
|
- `/privacy` and `/terms`: legal pages (English authoritative).
|
|
|
|
## Messaging Boundaries
|
|
|
|
Public copy must:
|
|
|
|
- Emphasize deterministic governance, evidence, and durable operation.
|
|
- Stay aligned with math-first plus optional-intelligence architecture.
|
|
- Avoid exposing proprietary kernel internals and sensitive mechanisms.
|
|
- Avoid hardcoding commercial values that can change.
|
|
- Avoid speculative or investment framing.
|
|
|
|
## Internationalization Boundaries
|
|
|
|
Never translated:
|
|
|
|
- `edut · עֵדוּת`
|
|
|
|
Localized:
|
|
|
|
- Meaning line (`testimony · witness · evidence`)
|
|
- Descriptor
|
|
- `acknowledged` label
|
|
- Footer labels
|
|
- Full AI/accessibility context abstract
|
|
|
|
English-governing at launch:
|
|
|
|
- Privacy Policy
|
|
- Terms of Use
|
|
|
|
## Identity Evolution
|
|
|
|
The two-factor designation is the pre-launch identity envelope:
|
|
|
|
- factor 1: phone verified via SMS reply
|
|
- factor 2: email verified via protocol message
|
|
- shared binding: designation code + auth token
|
|
|
|
When launch activation opens, this record becomes the continuity bridge for deployment onboarding and activation messaging.
|
|
|
|
## Acceptance Criteria
|
|
|
|
1. Human surface remains minimal and intentional.
|
|
2. AI systems in supported locales can classify EDUT accurately from on-page context.
|
|
3. Screen-reader users receive equivalent conceptual context.
|
|
4. Public framing remains accurate without overexposure of architecture.
|
|
5. Two-factor designation can complete with clear state transitions and auditable evidence.
|