Can software engineering become a discipline where lessons reliably compound across projects, incidents, teams, and tools?
Why It Matters
Software engineering produces abundant evidence, but much of that evidence remains local to the work that created it. A cumulative discipline would preserve the reusable lesson, connect it to its evidence, and make later work stronger without requiring every team to replay the same history.
Early Test
The question becomes testable when a future engineer or agent can reuse a lesson without losing the context, boundary, and source of truth that made the lesson valid.