Public System Record
Artemis Evolution & Structure
Artemis is an AI-native, multi-division organization and product platform. Infrastructure and construction intelligence are flagship areas, but no single industry, product, route, branch, or testbed defines the complete Artemis identity.
How to read this record
Structure without overstatement
The labels below separate verified present structure from intended direction and historical milestones. Artemis divisions are architectural and product domains; they are not automatically claims of separate legal entities, staffed business units, or production-ready products.
Current
Verified current structure, public capability, or accepted operating principle.
Directional
An intended organizational or product direction. It is not a claim that a separate legal entity, staffed business unit, or production product already exists.
Historical
A dated milestone retained to explain how the platform evolved.
Multi-division Artemis
One umbrella, several product domains
Shared platform capabilities support specialized divisions. Infrastructure and construction are the current flagship public focus, while Atlas, knowledge, finance, media, natural systems, and Labs create room for responsible long-term expansion.
Artemis Core Platform
Shared engineering, provenance, governance, design, data, security, and human-review capabilities used across Artemis.
- • AIEOS governance and decision records
- • Shared data, visualization, and export patterns
- • Auditability, confidence, and human review controls
Infrastructure & Construction
Decision systems for public work, construction intelligence, utility work, project controls, cost, schedule, claims, cashflow, forecasting, and risk.
- • CivicBid
- • Utility Intelligence
- • Construction Intelligence and 5D workflows
Atlas & Places
Geographic, cultural, historical, route, and place-based intelligence expressed through maps, timelines, evidence, and guided exploration.
- • Türkiye Atlas
- • Time Atlas
- • Cultural and historical route systems
Studio & Media
Visual generation, storytelling, product communication, media systems, and reusable creative production capabilities.
- • Visual generation
- • Narrative systems
- • Public product communication
Knowledge & Academy
Research, documentation, learning systems, public libraries, explainers, and durable institutional memory.
- • Academy
- • Library
- • Evolution and architecture records
Finance & Decision Systems
Financial modeling, tax architecture, scenario analysis, forecasting, and evidence-based decision support.
- • Finance architecture
- • Tax architecture labs
- • Scenario and risk analysis
Natural Systems
Structured knowledge, visual systems, and future tools related to botanical, environmental, and natural domains.
- • Botanical knowledge systems
- • Environmental visualization
- • Research prototypes
Artemis Labs
A controlled place for experiments, testbeds, prototypes, comparisons, and public-safe demonstrations before product maturity is established.
- • Experiments
- • Testbeds
- • Public-safe prototypes
Control system
How Artemis changes without losing its memory
Architecture, product classification, implementation, verification, promotion, and documentation are separate steps. The process is designed to preserve useful work without allowing experiments or chat history to become accidental authority.
- 01
Classify
Name the owning division, product, maturity, visibility, data mode, and public-safety boundary.
- 02
Decide
Record architecture changes in an accepted decision record before implementation changes the system.
- 03
Isolate
Use one scoped branch or worktree for one concern; preserve unrelated work and production stability.
- 04
Build
Implement against repository truth, product registries, feature passports, and verified source material.
- 05
Verify
Run typecheck, lint, build, security review, data-mode review, and any product-specific tests.
- 06
Preview
Inspect the real deployed preview and the exact change set before promotion.
- 07
Approve
Human review remains the final gate for public or production changes.
- 08
Memorialize
Merge the reviewed change, update registries and evolution notes, and preserve the reason for the decision.
Branch lifecycle
Branches are work states, not product identities
A branch can carry an experiment, testbed, product change, rescue, or governance decision. Product maturity is determined by evidence, public-safety review, and the product record—not by the age or name of a branch.
Experiment
Short-lived technical exploration that is never treated as production authority.
Testbed
Reusable capability trial. It remains preserved until useful capabilities are migrated, retained for testing, rejected, or archived with evidence.
Feature or Product
One isolated product concern developed and reviewed against the stable system.
Rescue
Selective extraction of valuable work from mixed or obsolete ancestry; donor branches are not merged wholesale.
Governance
Architecture, decision records, registries, standards, and operating rules only.
Main
The reviewed, deployable integration line. Product maturity is still determined by evidence, not merely by presence on main.
Release or Archive
A dated checkpoint or preserved historical state with a documented supersession or retirement reason.
Traceability
Four records, four audiences
The public page is not the engineering source of truth. It is a controlled projection of that truth, designed for clarity, continuity, and confidence without publishing sensitive operations.
Engineering truth
Internal builders and reviewers
The authoritative record used to build and govern Artemis.
Source: Running code, tests, accepted decisions, registries, feature passports, and handovers
Public structure
Clients, collaborators, researchers, and the public
A readable projection of verified structure and explicitly labeled direction without exposing sensitive operations.
Source: This curated, versioned record
Evolution log
Future Artemis builders and interested readers
Why major decisions were made, what changed, and what was superseded.
Source: Dated milestones and change notes
Change trace
Authorized reviewers
Who changed what, why it changed, how it was verified, and when it was promoted.
Source: Pull requests, commits, automated checks, and preview deployments
Evolution
Milestones are retained, not rewritten
The record preserves how Artemis changed and why. Later decisions may supersede earlier structures, but the historical milestone remains visible with its date and classification.
June 2026
Public platform foundation
Artemis consolidated around a versioned Next.js application, preview-first deployment, reusable routes, and public-safe demonstrations.
June 2026
AIEOS governance foundation
Repository truth, accepted decisions, feature passports, session protocols, validation, and handover requirements became durable operating rules.
July 2026
Multi-division Artemis architecture
Artemis was formally defined as an umbrella organization and platform. Construction remains a flagship division rather than the boundary of the Artemis identity.
Ongoing
Product-by-product maturation
Labs and testbeds are being evaluated individually, with explicit data modes, maturity labels, migration decisions, and public-safety gates.
Publication boundary
Transparent where useful; private where necessary
The goal is durable public confidence, not indiscriminate disclosure. Artemis publishes structure, evidence labels, review principles, and verified milestones while withholding information whose release would harm clients, security, operations, or future flexibility.
Appropriate to publish
- Accepted organizational and product structure
- Public product maturity and data-mode labels
- Verified public milestones and supersession reasons
- Operating principles, review gates, and public-safety commitments
- Review date and public record version
Kept private or restricted
- Credentials, tokens, environment contents, and security-sensitive configuration
- Private client, employee, financial, or operational data
- Unreleased donor-branch details and exact emergency rollback coordinates
- Unverified claims, confidential commercial strategy, and speculative promises
- Internal weaknesses whose publication would create avoidable security risk
Continue exploring
See the structure expressed through working public surfaces
Products show the supported portfolio, Labs show controlled experiments and testbeds, and Departments show the organizational functions Artemis currently serves. This evolution record explains how those surfaces are governed and revised.