-
Notifications
You must be signed in to change notification settings - Fork 0
feat(topic): logistic-normal ALR coordinates with true-parameter RMSE #48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 37 commits
9701b3d
130bc71
e76a0de
30ae9e0
bce4ac6
c95ebe1
5106f4b
0269df0
d70f5c7
0c3d88d
0d7c65f
f3540fa
ab29247
4ae9b5d
a52dd55
30c1d1f
2f08cdd
6fe6a78
d1f3dc3
4b54dc8
543982c
621cae0
8e88b33
f352e15
ff41714
45224e5
7769df7
7340399
26a9fde
578961a
1dd3953
b7214a8
16899f3
e337391
b3dc7da
6110d36
2e595d8
96e556f
c879a89
6510405
2084c84
04f05ea
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,84 +6,62 @@ implemented in Rust. | |
|
|
||
| ## Current implementation state | ||
|
|
||
| This branch keeps the Rust workspace quality foundation and the bounded | ||
| foundation crates. Domain crates expose only tested contracts: immutable | ||
| evidence, six-clock temporal values, event mentions/instances, relations, | ||
| membership, persistence, splits, simulation, validation, API DTOs, and the | ||
| predicted-versus-observed promotion gate. | ||
| This branch establishes the Rust workspace, quality-gate foundation, and the | ||
| longitudinal within/between decomposition capability. The eleven bounded crates | ||
| compile independently. `longitudinal_core` exposes within/between decomposition | ||
| and component RMSE APIs; the remaining crates expose no placeholder production | ||
| APIs, and domain behavior for them begins in Task 2 with immutable evidence | ||
| identifiers and source records. | ||
| This branch establishes the Task 1 Rust workspace and quality-gate foundation. | ||
| The twelve bounded crates compile independently but intentionally expose no | ||
| The eleven bounded crates compile independently; Task 1 includes the | ||
| implemented `encrypted_mapping` crate with AES-256-GCM sealing and | ||
| purpose-bound opening, while the remaining domain behavior begins in Task 2 | ||
| with immutable evidence identifiers and source records. | ||
| The eleven bounded crates compile independently. `derived_sensitivity` inherits | ||
| source Restricted/Internal classes onto topic, factor, and relation artifacts | ||
| and fails closed on unknown kinds; derivation and blanket PII masking are not | ||
| declassification. Other crates still begin domain behavior in Task 2 with | ||
| immutable evidence identifiers and source records. | ||
|
|
||
| The eleven bounded crates compile independently but intentionally expose no | ||
| placeholder production APIs. Domain behavior begins in Task 2 with immutable | ||
| evidence identifiers and source records. | ||
| This branch establishes the Rust workspace and quality-gate foundation. The | ||
| bounded crates compile independently; domain behavior includes immutable | ||
| evidence records, topic measurement, and cutoff-safe analysis execution. | ||
|
|
||
| ```text | ||
| crates/evidence_core | ||
| crates/semantic_core | ||
| crates/temporal_core | ||
| crates/event_core | ||
| crates/relation_graph | ||
| crates/membership_core | ||
| crates/persistence_postgres | ||
| crates/corpus_split | ||
| crates/tepp_simulation | ||
| crates/validation_core | ||
| crates/tepp_api | ||
| crates/prompt_source | ||
| crates/corpus_background | ||
| crates/modality_source | ||
| crates/analysis_engine | ||
| crates/assertion_clock | ||
| crates/available_clock | ||
| crates/checkpoint_authority | ||
| crates/citation_edge | ||
|
Comment on lines
+25
to
+50
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Unbalanced code fence in README breaks docs check The edit leaves README.md with 5 triple-backtick fences, an odd count. Prompt for agentsWas this helpful? React with 👍 or 👎 to provide feedback. |
||
| crates/copied_text | ||
| crates/style_source | ||
| crates/stopword_deletion | ||
| crates/copy_identity | ||
| crates/provider_receipt | ||
| crates/intake_authorization | ||
| crates/summarizes_edge | ||
| crates/outcome_order | ||
| crates/retrospective_edge | ||
| crates/payload_bound | ||
| crates/inferred_status | ||
| crates/support_edge | ||
| crates/system_clock | ||
| crates/event_clock | ||
| crates/assertion_clock | ||
| crates/corpus_background | ||
| crates/corpus_split | ||
| crates/cutoff_clock | ||
| crates/available_clock | ||
| crates/derived_sensitivity | ||
| crates/document_clocks | ||
| crates/revision_order | ||
| crates/encrypted_mapping | ||
| crates/citation_edge | ||
| crates/psychometric_fit | ||
| crates/subevent_containment | ||
| crates/event_clock | ||
| crates/event_core | ||
| crates/evidence_core | ||
| crates/inferred_status | ||
| crates/intake_authorization | ||
| crates/interpretation_gateway | ||
| crates/location_membership | ||
| crates/longitudinal_core | ||
| crates/membership_core | ||
| crates/membership_target | ||
| crates/modality_source | ||
| crates/model_selection | ||
| crates/network_analysis | ||
| crates/operational_log | ||
| crates/outcome_order | ||
| crates/payload_bound | ||
| crates/persistence_postgres | ||
| crates/prediction_contradiction | ||
| crates/prompt_source | ||
| crates/provider_receipt | ||
| crates/operational_log | ||
| crates/psychometric_fit | ||
| crates/relation_graph | ||
| crates/retrospective_edge | ||
| crates/revision_order | ||
| crates/semantic_core | ||
| crates/service_tls | ||
| crates/derived_sensitivity | ||
| crates/longitudinal_core | ||
| crates/stopword_deletion | ||
| crates/style_source | ||
| crates/subevent_containment | ||
| crates/summarizes_edge | ||
| crates/support_edge | ||
| crates/system_clock | ||
| crates/temporal_core | ||
| crates/tepp_api | ||
| crates/tepp_simulation | ||
| crates/topic_lineage | ||
| crates/network_analysis | ||
| crates/interpretation_gateway | ||
| crates/model_selection | ||
| crates/checkpoint_authority | ||
| crates/membership_target | ||
|
|
||
| crates/topic_measurement | ||
| crates/validation_core | ||
| ``` | ||
|
|
||
| ## Local verification | ||
|
|
@@ -118,3 +96,7 @@ this skeleton-only slice; it must never conceal uncovered production behavior. | |
|
|
||
| No release, production-readiness, GPU, database, or statistical-recovery claim is | ||
| made by this foundation slice. | ||
|
|
||
| The active stacked analysis-engine slice adds a bounded executable readiness path | ||
| from an accepted run to a digest-bound terminal artifact. It is not yet | ||
| implemented-main and does not replace scientific estimator contracts. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Duplicate rows in ARCHITECTURE foundation-crate table
The added rows for
validation_coreandtepp_apiduplicate the existing rows immediately below them, each now listed twice with conflicting descriptions.location_membershipis also re-added though it already appears in the file.Was this helpful? React with 👍 or 👎 to provide feedback.