ME / RESEARCH TOPIC
6 public research records in this topic.
Research note in development
Five possible stages for identity and adaptation in reusable components
Software can remember where it came from, what happened recently, and what it learned without being treated as a person. This developing research note proposes five stages for that kind of component identity. Its scenarios are candidate acceptance criteria, not evidence that a system has passed them.
Research note in development
Comparing a composable architecture with established systems practices
A software design can look new while being assembled from familiar ideas. This developing research note compares one composable architecture with microservices, actor systems, domain-driven design, formal methods, autopoiesis, and resilience research. Novelty judgments remain provisional until the comparisons and sources are verified.
Working paper — not peer reviewed
A practical inquiry into workflows, evidence, and AI-enabled test design
An assembly line is useful only when people can explain what entered it, what changed, and what came out. This paper asks how a generic automation factory could coordinate software work using workflows, clear evidence, and human-controlled release gates. It compares options and failure conditions instead of describing a finished system. AI-enabled test design is treated as one possible addition to established software practices.
Research note in development
A working model of persistence, relationships, and change in software components
A software component can change its state, surroundings, and collaborators while still being treated as the same component. This developing research note explores what that continuity could mean in a composable system. The model is an open question, not a claim about a completed implementation.
Research note in development
A bounded architectural proposal for managing context in composable systems
A language model needs enough context to act usefully, but unlimited memory creates cost, confusion, and privacy risk. This developing research note proposes a bounded component for selecting, carrying, and retiring context. Its interfaces, invariants, competing designs, and adoption consequences remain open to review.
Research note in development
Relationships, boundaries, feedback, and emergence as architectural lenses
Software systems are built, but their interactions can still produce effects that no single part controls. This developing research note explores an ecosystem analogy for architecture through boundaries, exchange, feedback, and emergence. The analogy remains provisional and will be revised where historical or technical evidence does not support it.