Garden / Topic

Architecture

18 connected archive items.

This topic is an index into the same repository-backed records used throughout the Garden.

Connected knowledge

49 total topics

NOTE / 01

Authority Is a Boundary

Systems become easier to trust when reasoning, capability and authority are kept separate.

Note • Architecture • AI • Security

NOTE / 02

Bounded Complexity Scales Better

A system can grow substantially without becoming unbounded when each new capability enters through explicit ownership and failure boundaries.

Note • Architecture • Systems • Python

NOTE / 03

Content Integrity Is Part of the Architecture

A connected knowledge archive is only as trustworthy as the relationships connecting its entries.

Note • Content • Architecture • Verification

NOTE / 04

Experience should expose the engineering model

A mature engineering archive should make identity, work, knowledge, evidence and history easy to understand without visual spectacle.

Note • UX • Architecture • Accessibility • Knowledge

NOTE / 05

CP22–CP27: From Portfolio Surface to Engineering Lab

What changed when the Lab moved from presentation quality toward connected knowledge, project intelligence, discovery and executable maintenance.

Note • Engineering • Architecture • Knowledge • Maintenance

NOTE / 06

Derived Views Should Stay Disposable

Indexes, catalogs and summaries are useful precisely because they can be rebuilt from authoritative state.

Note • Databases • Systems • Architecture

NOTE / 07

Knowledge Should Show Provenance

A knowledge archive becomes more trustworthy when ideas can point back to the engineering work that produced them.

Note • Knowledge • Provenance • Architecture • Documentation

NOTE / 08

Static Sites Can Record Live Work

A static site can feel current without pretending to provide real-time operational truth.

Note • Web Engineering • Documentation • Architecture

WRITING / 09

From Projects to Engineering Knowledge

The most durable knowledge in an Engineering Lab comes from extracting reusable principles from real systems, failures and decisions.

Writing • Engineering • Architecture • Learning

EXPERIMENT / 10

Project Knowledge Extraction

Experiment: can recurring engineering principles be extracted from real projects without turning the Lab into generic tutorial content?

Experiment • Knowledge • Architecture • Documentation

EXPERIMENT / 11

Repository-Backed Project Status

A small experiment in making project activity visible without adding a live status service.

Experiment • Architecture • Content Model • Static Sites • Verification

EVIDENCE / 12

Project Status Is Documentation, Not Live Health

The Lab deliberately treats project status as repository-backed documentation rather than a live operational signal.

Evidence • Evidence • Observation • Projects • Architecture

NOTE / 13

Capability Is Not Authority

A component may be capable of proposing an action without being allowed to authorize or perform it.

Note • AI • Security • Architecture

NOTE / 14

Complexity Is a Budget

Every new dependency and abstraction spends maintainability budget.

Note • Architecture • Simplicity • Maintainability

NOTE / 15

Verification Is a Boundary

Verification should be treated as a distinct responsibility rather than a final checkbox.

Note • Verification • Architecture • Reliability

WRITING / 16

Verification Before Autonomy

Why autonomous engineering systems need evidence and independent verification before they need more model capability.

Writing • AI • Verification • Systems • Architecture

WRITING / 17

Why Small Systems Win

A practical case for keeping personal engineering systems simple, local and inspectable.

Writing • Architecture • Simplicity • Systems

EXPERIMENT / 18

Architecture Boundary Test

Testing whether explicit ownership boundaries are clearer and safer than shared authority.

Experiment • Experiment • Architecture • AI