Skip to content

Latest commit

 

History

211 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ArcForges Design

This repository contains product requirements, system architecture, design decisions, and delivery planning for the ArcForges product family. It does not contain product implementation code.

Current work uses the formal requirements, architecture, planning and assurance under the effective accepted decisions. The original inputs completed their role; under P2-019 their bodies are not carried into this repository, and docs/deprecated-inputs/README.md identifies where they remain archived. They are deprecated, not current design authority or part of ongoing design-completeness audits. A missing current definition must be resolved in the formal design, not inferred from the archive.

Repository Structure

  • docs/requirements/: Product requirements and scope specifications.
  • docs/architecture/: System architecture specifications, topology, and component boundaries.
  • docs/decisions/: Architecture Decision Records (ADRs) capturing significant technical and design choices.
  • docs/planning/: Implementation delivery plans and work packages derived from accepted designs.
  • docs/assurance/: Design specifications covering quality, security, and acceptance criteria.
  • docs/deprecated-inputs/: Records where the deprecated original inputs are archived; their bodies are not carried into this repository. Excluded from active design, planning and audit scope.

Historical I1–I4 and input Stage citations identify the archived origin of a rule; they do not require reading or auditing those inputs again. Current definitions and accepted decisions stand on their own. Reference-source repositories and their review obligations are unaffected by this archival change.

License

ArcForges Design is licensed under the GNU Affero General Public License v3.0. See LICENSE.

Current architecture amendment

P2-009 adopts independent repositories and versioned native/managed packages, handwritten proto business RPC, a Native AOT C# business host, Kotlin/Jetpack Compose Android mobile under P2-010, and a sole Cloudflare AI Harness with Workers AI and R2. Start implementation at the planning entry; formal design decisions precede implementation and runtime proof.

P2-010 completes Android-only Kotlin/Compose planning, all Apache Contracts outputs including Maven, functional native ABI, full product/extension/policy behavior and cross-repository integration. Producer stages and the family completion review distinguish document closure from actual product/runtime/commercial evidence.

Current producer and local gRPC amendment: closure review. Use its current graph/contract evidence; earlier dated reviews retain their historical baselines.

Current design entry points

P2-012 defines Cloudflare hosting and independent embedded assistants. Start with project/package directories, client UX, D1, history, and scope/streams. Implementation is scheduled by the delivery model under P2-018: 51 active work packages are the obligation catalogue and the delivery graph schedules concurrent tasks.

Related repositories

This Design repository and the Plan repository (C:\MyFile\Projects\Plan) are the documentation pair governing the ArcForges family, per P2-019. Seven independent implementation repositories consume their accepted decisions: DesktopPlatform, Contracts, ArcScope, Cloud, AI, Web and Mobile.

Current coordinated repair: P2-014; see final findings verification. Earlier dated reviews retain their evidence baselines; real runtime and commercial gates remain separate and open.

About

The authoritative product vision, architecture, specifications, and implementation roadmap for the ArcForges product family.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors