You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 98bb12c
Browse filesBrowse the repository at this point in the historyBrowse files
π« Create one issue in the tracker a lexical context names
Supersedes this branch's deferred-finding-specific `<Issue>` with the
provider-neutral primitive #296 was amended to.
An issue provider does not necessarily own a Git repository β Atlassian issue
tracking owns none β so an Atlassian issue could never truthfully execute or
persist as a `git_host_effect`. `<Issue>` therefore has a boundary of its own:
its own contextual routing operation, `executablemd.workflow.issue`, and its own
durable effect type, `issue_effect`. What it reuses from #297 is the
observe-before-perform algorithm and the one-surface authority rule, internally.
#297's Git-host boundary goes back to owning Push and PullRequest only.
The component is four props β `title`, `description`, optional `tags`, optional
`assignee` β and `as` binds exactly `{ url }`. It renders nothing, so a paired
invocation is refused on the shape of the invocation, before the tracker is read
and before routing: content this element never renders would be discarded in
silence, and an issue created beside text nobody ever saw is worse than one not
created at all.
Deferral classification, approval, PullRequest provenance, rationale, dependency
impact and intended timing are gone from the primitive: they are workflow
policy, expressible in document structure or Issue middleware, and folding them
in made one team's review process part of the portable contract.
Where an issue goes is `<IssueTracker>`, the nearest lexical context, carrying a
credential-free URL and an optional provider discriminator. A nested tracker
replaces the whole tracker and never merges, because a child inheriting a
parent's `provider` while replacing its `url` would ask one service about
another's container. The context is composition data: the trusted host installs
an adapter-private ceiling beside its credentials, and a target outside it fails
before any provider observes anything.
A tracker is what a context names; a canonical target URL is the normalized
destination inside it, and that is the only place "target" survives β durable
identity, the natural key and every provider comparison use one spelling of one
destination.
The table of well-known hosts lives with the host rather than in the shared
boundary, and that placement is enforced rather than intended β DLC13 refuses a
provider's name in the shared coordination surface, and it was right to: the
first adapter naming itself in a shared contract is how a neutral boundary
quietly becomes one provider's. The shared surface carries the mechanism, the
host carries the policy, and `<Issue>` reads the answer through one
authority-free resolution.
Reconciliation keys `{ canonicalTargetUrl, runId, expansionId }` inside the
resolved provider's namespace; the fingerprint covers provider, target, title,
description, normalized tags and assignee. Tags are a code-point-sorted set
because order is not identity, absence of an assignee has one spelling
everywhere, and title is never identity. Retained Issue identities are published
beside the run the way Git-host ones are, so a fork adopts its inherited issue
rather than filing a second one.
Suites need no Workspace, Git or SQLite, and that is the contract rather than an
economy: a primitive that reaches a service owning no Git repository must not
need one to be tested. Their runtime exclusions are therefore gone.
Two test premises were wrong and are corrected rather than worked around: replay
does not re-read an edited document β that is a fork β so the divergence claim is
made against the fingerprint directly; and re-entering the shared surface from
inside a routing handler recurses, so the forgery attempts are made from outside
the finished invocation, where the surface's own default is what answers.
Copy file name to clipboardExpand all lines: architecture.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,8 @@ Existing documents and code get aligned to this section retroactively.
38
38
| Git capability | the contextual interface through which workflow infrastructure queries the Git repository associated with the current working directory |
39
39
| Git host | an external service that owns remote Git repositories and associated collaboration objects such as branches and pull requests. GitHub is one Git-host adapter. A Git host is distinct from the local Git capability and the trusted workflow host, and from an Issue provider |
40
40
| Issue provider | an external service that owns a collection of issues. GitHub and Atlassian Cloud are Issue-provider adapters. It is a separate boundary from a Git host because an Issue provider need not own a Git repository, and one that does not cannot truthfully persist as a Git-host effect |
41
-
| Issue target | the credential-free canonical URL naming the container new issues are created in, together with an optional explicit provider discriminator. It is replaceable composition data supplied by lexical context; it requests a destination and grants nothing |
41
+
| Issue tracker | what a lexical Issue context names: a credential-free URL for the container new issues are created in, together with an optional explicit provider discriminator. It is replaceable composition data; it requests a destination and grants nothing |
42
+
| canonical target URL | the normalized form of an Issue tracker's URL. One destination has one spelling, which is what durable identity, the natural key and every provider comparison use |
42
43
| provider discriminator | the stable lower-case name of an Issue provider. It selects which installed provider may accept a request, and is resolved from the canonical target URL when the context does not state one |
43
44
| printed error | an error printed into the document (`ErrorSegment`); data, not control flow |
44
45
| failure | an error that propagates (`ComponentFailure`, `DocumentationError`) |
@@ -2472,7 +2473,7 @@ Status is measured against main.
2472
2473
| transactional Git effects (`Git.Switch` / `Git.Add` / `Git.Commit`) | publish local Git mutations with their journal result; the enclosing Repository and the contextual working directory select which retained checkout one runs in, and neither observation carries authority β the observed record is compared with the retained row and the directory with the checkouts that row holds, so a failure of authority, of retained state or of an unrecognized native condition fails the run instead of publishing a result | built on the #294 stack, Deno provider only |
2473
2474
|`Git.Push`| publishes the selected checkout's exact current named branch and commit to the same branch on the retained Repository's canonical `origin`, reconciled through the shared Git-host state machine rather than through a Workspace transaction: no props and no component result, no force, no upstream mutation and no implicit staging or committing; the durable request and record carry the Repository's filtered identity without its checkout path, and the transport runs in a provider-owned isolated control repository reading the checkout's objects through an object-source attachment whose alternates chain and object tree are proven contained before the first remote observation, aimed at the exact private retained locator | built on the #370 stack, Deno provider only |
2474
2475
| `<PullRequest>` | upserts one pull request of the selected checkout's current named branch, reconciled through the shared Git-host state machine: a required `title`, an optional positive-integer `number`, an optional `base` defaulting to the Repository's retained initial branch, an optional `draft`, and the rendered content as the body; it renders nothing and returns stable evidence through `as` β the filtered Repository identity, the provider's own stable pull-request identity, number, URL, open state, and the head and base SHAs of the snapshot it finished at. Without a number it creates one pull request for the head/base pair or adopts the compatible one an interrupted attempt left; with a number it brings that exact pull request's title, body, draft state and base to what the request says, records a no-op when they already match, and refuses a number belonging to another repository, opened from another head, or no longer open. It never pushes, never rewrites a head, and never reopens, merges or comments. The run must already hold its own successful `Git.Push` result for that exact Repository identity, head branch, destination ref and commit β proven by a scan that requires the record's natural key, inputs and result to describe one publication β and a missing, conflicting or unreadable one fails locally before the Git host is observed; the first adapter works over `github.com` on REST plus the two GraphQL draft transitions, selected from the private retained locator, credentialed from `GH_TOKEN` then `GITHUB_TOKEN`, issuing each required mutation at most once per attempt and deciding the outcome by one observation, with the locator, endpoint, credential and payload confined to the per-invocation provider closure | built on the #295 stack, Deno provider only |
2475
-
| `<Issue>` | creates one issue in the container the nearest lexical Issue context names, through a boundary of its own rather than the Git host's: exactly `title`, `description`, optional `tags` and optional `assignee`, no children, no repository/url/provider/token/label/milestone/project/comment/close or approval prop, it renders nothing, and `as` binds exactly `{ url }`. The context carries a credential-free `url` and an optional `provider`; the URL is canonicalized and the provider resolved from a table of well-known hosts the trusted host installs beside its adapters β `github.com` to `github`, `*.atlassian.net` to `atlassian` β so the shared boundary carries the mechanism and never a provider's name, unless the context states one, which wins and never falls back on refusal. A nested context replaces the whole target for its descendants and members are never merged. The context is composition data, not authority: the trusted host installs an adapter-private target ceiling beside its credentials, and a target outside it fails before external observation. Routing is one request-only contextual operation, `executablemd.workflow.issue`, under #297's one-surface authority rule. Identity is engine-derived; the natural key is `{ canonicalTargetUrl, runId, expansionId }` within the resolved provider's namespace and the fingerprint covers provider, canonical URL, title, description, normalized tags and assignee. Tags are deduplicated and code-point sorted because order is not identity, and title is never identity. Reconciliation is journaled as `issue_effect`, retaining the normalized request, provider name, pre-state, observations, decision and normalized result β no credential, payload, endpoint or host path. Deferral classification, approval and PullRequest provenance are workflow policy expressed in document structure or Issue middleware, not members of this primitive | built on the #296 stack; GitHub adapter, Deno host |
2476
+
| `<Issue>` | creates one issue in the container the nearest lexical Issue context names, through a boundary of its own rather than the Git host's: exactly `title`, `description`, optional `tags` and optional `assignee`, no repository/url/provider/token/label/milestone/project/comment/close or approval prop, it renders nothing, and `as` binds exactly `{ url }`. A paired invocation is refused on the shape of the invocation, before the tracker is read and before routing. The context carries a credential-free `url` and an optional `provider`; the URL is canonicalized and the provider resolved from a table of well-known hosts the trusted host installs beside its adapters β `github.com` to `github`, `*.atlassian.net` to `atlassian` β so the shared boundary carries the mechanism and never a provider's name, unless the context states one, which wins and never falls back on refusal. A nested context replaces the whole target for its descendants and members are never merged. The context is composition data, not authority: the trusted host installs an adapter-private target ceiling beside its credentials, and a target outside it fails before external observation. Routing is one request-only contextual operation, `executablemd.workflow.issue`, under #297's one-surface authority rule. Identity is engine-derived; the natural key is `{ canonicalTargetUrl, runId, expansionId }` within the resolved provider's namespace and the fingerprint covers provider, canonical URL, title, description, normalized tags and assignee. Tags are deduplicated and code-point sorted because order is not identity, and title is never identity. Reconciliation is journaled as `issue_effect`, retaining the normalized request, provider name, pre-state, observations, decision and normalized result β no credential, payload, endpoint or host path. Deferral classification, approval and PullRequest provenance are workflow policy expressed in document structure or Issue middleware, not members of this primitive | built on the #296 stack; GitHub adapter, Deno host |
2476
2477
| workflow lifecycle inspection and control | reads status/list/history without advancing a run, enforces the executor lock, refuses live cancellation, cancels non-live runs under that lock and deletes retained state | built on the #367 stack |
2477
2478
| historical authored source | retains an authored durable operation's normalized `SourcePosition` beside its identity, and history parses it or refuses the entry | built on the #367 stack |
2478
2479
| history fork | creates a new run from one compatible checkpoint and retained Workspace root, under a new immutable definition and normalized props | built on the #368 stack, Deno provider only |
0 commit comments