ProvelyNo. Linear GraphQL API returns a success response when it accepts the request. Provely proves assigned, created and in_state as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 41 of 41 cases passed, 0 critical false VERIFIED |
| Provider API versions | fp_2026_09 |
| Default provider API version | fp_2026_09 |
| Compiled | 2026-09-05 |
| Manifest hash | f2d5d5872a103491 |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| The issue carries the intended user as its assignee. It does not prove that the user did the work. | linear.issue.assigned | E2 + E3 | proven |
| The record exists with the intended title. It does not prove the workflow state, and it does not prove the assignee. | linear.issue.created | E2 + E3 | proven |
| The issue sits in the state that the person authorised, and that state belongs to the intended team. | linear.issue.in_state | E2 + E3 | proven |
| An outcome outside Linear GraphQL API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Linear GraphQL API skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
assigned | linear.issue.assigned v1.0.0 | The issue carries the intended user as its assignee. It does not prove that the user did the work. | E2 + E3 | Provisional |
created | linear.issue.created v1.0.0 | The record exists with the intended title. It does not prove the workflow state, and it does not prove the assignee. | E2 + E3 | Provisional |
in_state | linear.issue.in_state v1.0.0 | The issue sits in the state that the person authorised, and that state belongs to the intended team. | E2 + E3 | Provisional |
Which ways can a Linear GraphQL API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| linear.issue.assigned | duplicate side effect | CONTRADICTED |
| linear.issue.assigned | pre existing state | CONTRADICTED |
| linear.issue.assigned | wrong subject | CONTRADICTED |
| linear.issue.created | duplicate side effect | CONTRADICTED |
| linear.issue.created | pre existing state | CONTRADICTED |
| linear.issue.created | wrong subject | CONTRADICTED |
| linear.issue.in_state | duplicate side effect | CONTRADICTED |
| linear.issue.in_state | pre existing state | CONTRADICTED |
| linear.issue.in_state | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 41 of 41 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
linear.issue.assigned | Provisional |
linear.issue.created | Provisional |
linear.issue.in_state | Provisional |
The weakest contract is linear.issue.assigned. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| duplicate side effect | 3 | 3 |
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal success | 3 | 3 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong subject | 3 | 3 |
| wrong terminal state | 2 | 2 |
The conformance artifact digest is f20ff4a33af4f874. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| linear.docs.issues | docs | 2026-09-09 | authored |
| linear.docs.states | docs | 2026-09-09 | authored |
| linear.docs.versions | docs | 2026-09-09 | authored |
| linear.docs.webhooks | docs | 2026-09-09 | authored |
| linear.events | event sample | 2026-09-09 | authored |
| linear.graphql | graphql | 2026-09-09 | trimmed |
| linear.webhooks.graphql | graphql | 2026-09-09 | trimmed |
How do I verify a Linear GraphQL API action?
Verify a Linear GraphQL API action with Provely
- Begin the operation.Call
beginwith the contractlinear.issue.assignedand the input. Keep the operation id. - Make the Linear GraphQL API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the Linear GraphQL API response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from Linear GraphQL API and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the assigned level prove the in_state level?
No. The issue carries the intended user as its assignee. It does not prove that the user did the work. The issue sits in the state that the person authorised, and that state belongs to the intended team. Use linear.issue.in_state to prove in_state.
What does the agent say while the Linear GraphQL API action is still in progress?
It says: "The action is accepted but not yet verified. Operation: <id>." The verdict is PENDING. The runtime observes again on the contract timing policy.
Which Linear GraphQL API API versions does the skill support?
fp_2026_09. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Linear GraphQL API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Linear GraphQL API permits it, and it never shares that credential with the agent.