LIGHTHOUSE / ENGINEERING BASELINE

A clear path to engineering excellence.

Proven techniques and best practices for a practical, AI-driven SDLC.

See the baseline Choose an adoption route

The public story is generated from ProductShape, ArcShape and the Lighthouse package contracts.

01AdoptableClear routes for new and existing projects.

02Evidence-backedGuidance stays close to executable checks.

03Profile-basedUse the stack support your product needs.

04Human-ownedAutomation reports; maintainers decide.

IDENTITY / SIGNAL BLUE

The signal has a color.

Signal blue is the Lighthouse accent for the beam, the grid and the moments that need to stand out.

Signal blue#4DA3FF

01 / AUTHORITIES

One story, two sources of truth.

ProductShape defines what to build. ArcShape records how the system is shaped.

PRODUCT

Product model

The generated ProductShape snapshot shows the accepted product model and its delivery capabilities.

Open the product snapshot ARCHITECTURE

Architecture snapshot

The ArcShape reader separates the implemented Lighthouse repository from the target initialized application.

Open the architecture snapshot

IMPLEMENTED TODAY

Lighthouse repository

CLI, UI package, .NET reference profile, verification, gallery and this generated site.

TARGET ADOPTION

Initialized application

Predictable structure, selected profiles, Aspire composition and project-owned decisions.

02 / DELIVERY FLOW

Make the next step visible.

The target SDLC package keeps product, design, implementation and evidence connected.

Triage

Assess urgency, complexity, dependencies and blast radius.

Refine

Turn the work item into a bounded, reviewable change.

Propose

Describe the solution and its affected contracts.

Implement

Build from red to green with the applicable checks.

Integrate

Review the gate, merge the change and preserve evidence.

Review

Record what the delivery taught the project.

TRACKER STATE

Labels expose state and route requests such as Ready, Planned, WIP and Done. The workflow does not infer state from issue prose.

SDLC package contract · the CLI projects it; the host runs each stage.

03 / FOUNDATION

Engineering expectations you can adopt.

One baseline for repository practice, profiles and interface work.

Repository baseline

Concise conventions, evidence and verification keep the repository understandable to people and agents.

Read the contributor entrypoint

Clear boundaries

Product intent, architecture, agent skills and operational tooling keep their own authorities and managed files.

See the boundary decision

Lighthouse .NET profile

A creator, use-case contracts, Aspire orchestration and Roslyn guardrails give .NET work a small, testable starting point.

Explore the profile

Visual system

Semantic tokens and native CSS recipes provide a calm interface foundation with light, dark and system appearance.

Read the design guide

04 / ADOPTION

A smaller loop for better decisions.

The baseline meets a project where it is.

Choose a route

Start with the profile that matches the work. Keep the rest optional.

Adopt the contract

Run the initializer, inspect its managed paths and record exceptions with an owner.

Verify the result

Run the local checks, review the evidence and let a maintainer accept the change.

LOCAL LOOP

Keep the feedback close to the repository.

$ lighthouse init
$ lighthouse verify

05 / ROUTES

Start where the work is.

Use one entrypoint, then add only what the product needs.

Backend