NouraIn development

The reasoning layerabove your codebase.

Noura is a software provenance platform being built to preserve the reasoning behind software. Git remembers what changed. Noura is designed to remember why.

See the concept Current status

Problem · 01

The missing layer.

Software preserves the artifact. Intent slips away.

A codebase keeps evolving, but its reasoning becomes fragmented across commits, pull requests, documents, conversations, and individual memory. The implementation remains while the story behind it fades.

Code

What exists

Code shows the current implementation. It cannot explain why it lives here, which constraints shaped it, or why another approach was rejected.

Git

What changed

Commits and pull requests preserve activity over time. They rarely preserve the complete reasoning that connected those changes.

Documentation

What was written down

Documentation captures what someone remembered to record. It becomes incomplete, outdated, or separated from the software it describes.

Product flow · 02

From repository activity to software memory.

Git remains the source of truth. Noura is meant to sit above it with change linked to human intent. This is the intended product flow.

Source · 02.1

Connect the repository

Connect a repository and map its commits, pull requests, branches, and file changes.

Evolution · 02.2

Build the timeline

Related changes read as a story of how the system evolved and not just a chronological feed of activity.

Reasoning · 02.3

Create decision records

Teams capture context, options, the decision, reasoning, tradeoffs, assumptions, and source changes.

Memory · 02.4

Build software memory

Events, decisions, notes, and threads connect into memory that can explain why the software became what it is.

Repository events + confirmed human context → software memory

Concept · 03

Git shows activity. Noura shows evolution.

A repository timeline connected to a decision record — product direction, illustrated.

noura.app/projects/platform-core

Authentication evolution

A thread assembled from source changes and confirmed context

Jan 2026
Original authentication system
Internal JWT flow introduced
Mar 2026
Limitations discovered
Multiple clients needed external providers
Apr 2026
Migrated to OAuth
Decision DR-018 · PR #482

Role of AI · 04

AI is the assistant. Software memory is the product.

Noura is not an AI documentation tool, a coding assistant, or a generic chat layer. AI reduces the effort required to preserve and retrieve reasoning; it does not become the source of that reasoning.

04.1

Notice meaningful change

Noura is intended to surface repository activity that may represent an architectural decision and ask for context.

04.2

Help structure reasoning

Developers explain a choice naturally. AI helps organize that input into a useful decision record.

04.3

Answer from evidence

Questions should be answered from connected commits, records, notes, and threads with the source trail kept visible.

04.4

Keep people authoritative

AI can surface and structure context. It cannot invent the intent behind a decision or replace human confirmation.

Development · 05

Currently in focus.

Building the reasoning layer carefully.

Noura is in active development. Current focus: the provenance model, the path from repository change to decision record, and assistance that stays grounded in preserved evidence.

Core

Defining the provenance model

Shaping how projects, repository events, decisions, notes, and evolving threads connect without duplicating Git.

Workflow

Mapping the repository-to-decision flow

Defining the path from connected change to a confirmed decision record and a readable software timeline.

Assistant

Testing assistance without invention

Using AI to surface important changes, help structure explanations, and answer questions from preserved evidence.

Invitation · 06

The reasoning layer is still taking shape.

Noura is in active development and shaping software provenance carefully before opening access.

Meet the studio Write the studio

What we're building toward

A focused product surface01
Proven repository workflows02
A clear path to access03