Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

fix: correct repo identity — this is cic-storage, not cic-primitives - #2

Merged
sinkog merged 1 commit into
develfrom
fix/repo-identity
Sep 7, 2026
Merged

sinkog merged 1 commit into
develfrom
fix/repo-identity

Conversation

@sinkog

@sinkog sinkog commented Sep 7, 2026

Copy link
Copy Markdown
Member

Same identity-drift fix as cic-network PR #2: project.yaml/README.md/.hu.md/CLAUDE.md/ai/*.md all still claimed this repo is cic-primitives — a verbatim, never-adapted scaffold copy from 2026-04-30.

Unlike cic-network, this repo has no domain-specific composition yet — schemas/examples/ only holds cic-primitives' own generic kubernetes-pod.yaml demo. Docs now say that plainly instead of claiming this repo did the primitive layer's own bootstrap work.

Not touched: schemas/atomic/*.yaml, schemas/aggregate/*.yaml — legitimately inherited primitive definitions.

🤖 Generated with Claude Code

project.yaml, README.md/.hu.md, CLAUDE.md, and ai/*.md/ai/PROMPTMAP.yaml all
still claimed this repo IS cic-primitives — a verbatim, never-adapted
scaffold copy from 2026-04-30 (main_branch: primitives/main,
x-cic.repo_type: primitive, README title # cic-primitives, etc.), matching
what was found and fixed the same way in cic-network (PR #2 there).

Corrected the identity fields. Unlike cic-network, this repo has NO
domain-specific composition yet — schemas/examples/ only holds
cic-primitives' own generic kubernetes-pod.yaml demo, not storage-specific
work — so the docs now say that plainly instead of describing cic-storage as
though it had done the primitive layer's own bootstrap (atomic/aggregate
schemas, 14 design decisions, a 'done' task queue — all real, all
cic-primitives' own history, not this repo's). Disclaimers added rather
than deleting that inherited content.

Not touched: schemas/atomic/*.yaml, schemas/aggregate/*.yaml (legitimately
inherited primitive definitions).

---
[signing-metadata]
key = cic-my-sign-key
signature = vault:v1:MEQCIB3hhxKJTKXpISRWIQnlDhSC6Vzuqj6YRumQ8ilaUkWhAiBInYqx8+hApsN0LNkEVZKda7dtYR4CXS3GVGQ9x3fnTA==
hash-algorithm = sha256
digest = EEbG2yjrF1ibdSvQ3xwFowsf8+HlcjEtrj4dnC47W3E=

[certificate]
-----BEGIN CERTIFICATE-----
MIICBjCCAaygAwIBAgIUSnRMR6RPnEbg296XWPOqq/u5PCwwCgYIKoZIzj0EAwIw
QzELMAkGA1UEBhMCSFUxGTAXBgNVBAoMEENlbnRyYWxJbmZyYUNvcmUxGTAXBgNV
BAMMEENJQyBEZXZlbG9wZXIgQ0EwHhcNMjYwMzIwMTMyMjU5WhcNMjYxMjMxMTMy
MjU5WjBFMQswCQYDVQQGEwJIVTEZMBcGA1UECgwQQ2VudHJhbEluZnJhQ29yZTEb
MBkGA1UEAwwSR2Fib3IgWm9sdGFuIFNpbmtvMFkwEwYHKoZIzj0CAQYIKoZIzj0D
AQcDQgAEIG2CVmTfmLB9pLLclj7YmP2eedAjklpy4LGrU2ijoiy6Xqpuybv7OgJe
i+ez31s65NEV8+X/ByeX1cstR988z6N8MHowCQYDVR0TBAIwADAdBgNVHQ4EFgQU
yZN6AIX/TNnIJ9GwAa/NRN3ujHAwHwYDVR0jBBgwFoAUXn6CHYzPUqU4JVP8g+OS
WeDYjhcwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF
BQcDBDAKBggqhkjOPQQDAgNIADBFAiEA+bFzXRoJ4PCQbhAAtpkcMjt0vNj5rEW0
lOMBGDNyaWkCIB1vmM7PcZzv/c9bIrxF5kqv6QXomouhByUfeNUTbpKW
-----END CERTIFICATE-----
@sinkog
sinkog merged commit 625eba7 into devel Sep 7, 2026
1 check passed
@sinkog
sinkog deleted the fix/repo-identity branch September 7, 2026 06:31
sinkog pushed a commit that referenced this pull request Sep 7, 2026
…devel

PR #2 (625eba7) documented cic-storage as having 'no storage-specific domain
composition yet' — this was checked against devel/main only and was false.

git ls-remote origin (+ GHCR confirmation) shows storage/main (e97c311) and
storage/releases/v0.1.0 (cdb5f45) carry real, already-signed work never
merged into devel: StorageResource + StorageAdapter (block volume,
hypervisor/SAN/cloud, capability-based conformance), published to GHCR as
v0.1.2-src2026.

Corrects README.md/README.hu.md/CLAUDE.md/ai/SYSTEM_CONTEXT.md/ai/PROMPTMAP.yaml
to state both realities plainly: devel's own StorageBucket draft (D-015,
PR #3, closed unmerged) is experimental and unreconciled with the real,
pre-existing StorageResource work living on a divergent branch. Records the
gap and the open reconciliation question as D-016 in ai/DECISIONS.md — no
merge/recovery decision has been made yet, this commit only fixes the false
claim.

---
[signing-metadata]
key = cic-my-sign-key
signature = vault:v1:MEUCIQDpi19YCvvOKuzbCeUmXuWzxW1Ufp9jKpMdTg5+QdUePAIgEE2lsw1r9kcKPUdAFnc3wNV5deF0ICwHisKDnnu8WTU=
hash-algorithm = sha256
digest = BcLcZlv3movzFQmLKCBke3vv/tHFnHzxpcRdwc2tIyM=

[certificate]
-----BEGIN CERTIFICATE-----
MIICBjCCAaygAwIBAgIUSnRMR6RPnEbg296XWPOqq/u5PCwwCgYIKoZIzj0EAwIw
QzELMAkGA1UEBhMCSFUxGTAXBgNVBAoMEENlbnRyYWxJbmZyYUNvcmUxGTAXBgNV
BAMMEENJQyBEZXZlbG9wZXIgQ0EwHhcNMjYwMzIwMTMyMjU5WhcNMjYxMjMxMTMy
MjU5WjBFMQswCQYDVQQGEwJIVTEZMBcGA1UECgwQQ2VudHJhbEluZnJhQ29yZTEb
MBkGA1UEAwwSR2Fib3IgWm9sdGFuIFNpbmtvMFkwEwYHKoZIzj0CAQYIKoZIzj0D
AQcDQgAEIG2CVmTfmLB9pLLclj7YmP2eedAjklpy4LGrU2ijoiy6Xqpuybv7OgJe
i+ez31s65NEV8+X/ByeX1cstR988z6N8MHowCQYDVR0TBAIwADAdBgNVHQ4EFgQU
yZN6AIX/TNnIJ9GwAa/NRN3ujHAwHwYDVR0jBBgwFoAUXn6CHYzPUqU4JVP8g+OS
WeDYjhcwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF
BQcDBDAKBggqhkjOPQQDAgNIADBFAiEA+bFzXRoJ4PCQbhAAtpkcMjt0vNj5rEW0
lOMBGDNyaWkCIB1vmM7PcZzv/c9bIrxF5kqv6QXomouhByUfeNUTbpKW
-----END CERTIFICATE-----
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant