Software developed from recurring system problems
1DevTeam develops products when the underlying problem, architecture, and expected reuse justify a durable software system. Product maturity is stated according to current evidence rather than implied through presentation.
Current portfolio
Ajenda AI is the current flagship product under active private development. G.R.A.F.T.+ and G.R.A.F.T.1st are applied R&D outputs whose product objectives remain separate from the conclusions of the research program that may inform them.
Ajenda AI
Ajenda AI is an execution system for converting goals into structured missions, plans, tasks, approvals, and controlled actions. Its architecture includes explicit authority boundaries, persistent mission state, capability selection, review paths, recovery behavior, execution evidence, and controlled interaction with connected systems.
Explore Ajenda AICurrent status
Ajenda AI is under active private development and is locally operational. It is not represented as a generally available hosted service or as a customer deployment.
Applied R&D outputs
G.R.A.F.T.+ and G.R.A.F.T.1st
These systems emerge from architecture and repair problems examined in the formal R&D program. Research can support, narrow, change, or contradict the assumptions behind either system; product direction does not determine the study's conclusions.
G.R.A.F.T.+
G.R.A.F.T.+ reconstructs a public GitHub repository at one SHA into evidence-linked facts and one downloadable pack so an external language model can reason over inventory, contracts, dependencies, routes, wiring, and intent. Residuals stay visible. It is a fact substrate, not a planner and not merge authority.
Operating model
Public repository → reconstruct one SHA → download the fact pack → give the receipt and ASCII topology to an AI → let the AI calculate reach, proof, risk, and architecture.
G.R.A.F.T.1st
G.R.A.F.T.1st is intended to model the architecture of a software system before implementation begins. The objective is to represent contracts, nodes, models, ownership, dependencies, state, boundaries, and system interactions in a form that can be reasoned over before the first implementation decisions are committed to code. Its relationship to implementation quality remains a research and development question rather than an established conclusion. This lab is G.R.A.F.T.+ only.
Operating model
Intended system → explicitly model the architectural problem → reason across the complete design → build against that model.
Intended future relationship
G.R.A.F.T.1st → intended architecture → implementation → G.R.A.F.T.+ → reconstructed architecture → drift analysis
This remains a development hypothesis, not a completed research finding.
Read the R&D program