Architecture in plain language

Technical Overview

Now I See It is being built in stages: one clear vertical slice first, then wider expansion through shared structure, validation, and governed growth.

This page is high-level on purpose. It is meant to orient collaborators and AI agents without overclaiming unfinished internals.

A practical overview

Now I See It is being developed as a modular, staged ecosystem. The immediate aim is not to make every domain live at once. The immediate aim is to build one clear vertical slice well, with governed structure that can support safer expansion later.

Implementation principle

Rule-based first

Early routing, scoring, and summarisation should remain deterministic and inspectable. Explainability matters for educational trust and maintainability.

Scaling principle

Structure before sprawl

New domains should be added through shared schema, validation, registries, and clear persistence rules rather than by copy-pasting ad hoc patterns.

Public-facing architecture themes

Desktop-first thinking: Designed with practical deployment realities in mind, including constrained or mixed-connectivity contexts.
Connected components: Smart Start, scenarios, evidence, summaries, educator support, and future sensor-linked work are meant to fit into one coherent ecosystem.
Versioned growth: Capabilities move from seed concept to stable slice to broader coverage through staged implementation and feedback.
Transparent AI boundaries: AI may assist with language and support layers, but hidden AI authority is not the design goal.

Technical honesty

This public site does not over-specify internal implementation. It exists to explain the architecture at a useful level while remaining truthful about what is already built and what is still being staged.