Decide provider and daemon execution model#111
Open
jmcte wants to merge 4 commits into
Open
Conversation
Expose a deterministic metadata-only provider registry through JSON and text output, covering every current Apple-data command family with maturity, source, permission, sensitivity, capability, and polling declarations. Document the v1 compatibility policy.\n\nCloses #89.
Expose a versioned external manifest derived from the provider registry, document bounded local wrapper policy, and cover it with synthetic contract tests. Co-authored-by: Hermes <Hermes-omt@protonmail.com>
Build universal macOS DMGs with stable code identity, notarization, stapling, checksums, release evidence, and governed secrets. Reconcile v0.2 versioning, bootstrap release policy, onboarding, installation, and security decisions.
Compare CLI, daemon, helper, and delegated models across lifecycle, IPC, TCC, isolation, archives, signing, and recovery. Classify every provider and keep daemon mode and mutations outside the default boundary pending human approval.
jmcte
marked this pull request as ready for review
July 13, 2026 07:29
jmcte
enabled auto-merge (squash)
July 13, 2026 07:29
Hermes-omt
reviewed
Jul 17, 2026
Hermes-omt
left a comment
Contributor
There was a problem hiding this comment.
Blocked pending branch refresh: head 0fca069 is behind current main d7f88dc and GitHub reports mergeable=false, mergeable_state=dirty. Please rebase/update the PR branch, resolve conflicts, and wait for fresh CI before re-review. Exact-head local inspection and swift test passed (110 tests); public reviews and inline review comments are empty.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Governing Issue
Refs #83
This issue is explicitly human-required. The PR proposes a decision but does not mark the ADR accepted or close the issue before non-author product, architecture, and security approval.
Validation
Relevant local checks passed
Required PR checks are expected to satisfy
CI GateSkipped checks are explained below
git diff --check— passedbash scripts/ci/run-fast-checks.sh— passed; 110 tests, 88.58% source coverage, mutation checks, debug and release buildsNo checks skipped.
Bootstrap Governance
CONTRIBUTING.md,.github/PULL_REQUEST_TEMPLATE.md, anddocs/bootstrap/onboarding.mdwhen applicableNo contributor guidance changed.
Flow Contract
Flow Merge Readiness
Next actors: product, architecture, and security reviewers must accept or amend the proposed decision.
Merge Automation
gh pr merge --auto --squash, or the reason it is unavailable/unsafe is noted belowAuto-merge is intentionally disabled for the human-required architecture decision.
Notes