Reference Projects

• AsterDrive: the larger product surface, useful for complete storage, external-auth, task, database, and metrics integration examples.
• AsterYggdrasil: a lighter product boundary, useful for seeing which task, runtime, API, and middleware responsibilities stay in the product repository.

The Chinese documentation contains the complete crate-by-crate integration notes.

Observability consumer evidence index

Checked on 2026-10-17. Forge owns public mechanisms, pinned revisions and consumer evidence references. Drive owns its current capability/configuration contract. A master link means the current branch; pinned links establish only that snapshot, not release or production status. The full product matrix is not duplicated here.

Field	AsterDrive evidence
capability / owning crate	aster_forge_metrics: instance provider, typed instruments, Prometheus / OTLP HTTP/protobuf metrics and lifecycle; aster_forge_observability: Actix exposition; aster_forge_logging: local text/JSON subscriber and guard
Forge revision	869756f0605c898420a28d3d45006cc33a87d17c; metrics, observability, logging contracts
consumer / revision / lock source	Drive 4b857c0fc3a27941b36861657225f20786c3831b; Cargo.lock, root features, product crate features; pinned Git revision, no local patch
integration status	Instance metrics, dual export and scrape authentication merged in Drive #642; local logging integrated; OTLP traces/logs, cross-node traces and continuous profiling platform export are not integrated
adapter / call sites	Recorder, static config, health route, authentication, injection, shutdown, logging initialization
validation evidence	#642 records local four-mode feature/config checks, primary/follower endpoint/authentication, schema/Grafana, upload and three-database migration tests. It used Forge 2beaf986f1740629d3fd8913f865e4134d31e203 and did not wait for new CI. Those results do not establish a full rerun at the current revision; repeatable commands
rollout evidence	The image workflow defines -metrics, not proof of a published tag/digest. Downloadable artifacts and production deployment were not verified here. OTLP uses Drive's documented source/custom-image path
next issue	Forge #44: library/template acceptance; Forge #45 → Drive #638: traces; Forge #46 ↔ Drive #639: source/evidence

Update and validation ownership

• PRs changing public APIs, features, export protocols, schema or lifecycle update crate docs, tested examples and this index. Link affected consumers' pinned revisions/PRs and actual test results. Consumers own product configuration and role matrices.
• Merge, dependency resolution, library tests, consumer tests, release artifacts and production rollout are distinct evidence. Mark unknowns unverified and local patch/WIP explicitly; neither is published Git adoption.
• Run bun run docs:build in docs/ to run docs:check-evidence for required index fields, bilingual pinned revisions and Forge source paths, then check internal links and build rustdoc. Reuse consumer test scripts without fetching every product on each Forge PR. Drive's offline documentation check constrains bilingual baselines and lock revisions; static checks do not establish protocol behavior or collector delivery.
• #44's core is implemented; remaining acceptance does not mean Drive is unmigrated. #45's tracing/layers remain future work. Current init_logging() installs a global subscriber; existing logging spans do not establish OTel export support.