# `Cause.seq`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Property of [`Cause`](Cause.md) · stable · since 2.0.0

```ts
readonly seq: number;
```

+1 per commit of any kind; the current [`session.seq`](Session.seq.md) on an equal write's 'history:changed'.
Commits are numbered in commit order, not call order: a write called before another can commit
after it (a write that loads, or one waiting in the write queue; spec section 6.1, O2), so a
`seq` above the [`session.seq`](Session.seq.md) you read at some call doesn't mean the write was called after
that call. Compare it with a commit's own `seq` (a Report's) instead.

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `seq` names no product |
| 2. A precedent | pass (through its owner [`Cause`](Cause.md)): a correctness rule (rows `X2`) |
| 3. Two apps, or labs | pass (through its owner [`Cause`](Cause.md)): 16 apps (ledger: app-4fd23bc869, app-822bb9d6aa, app-8675b3225c, app-b362a81c85, app-bcb7ef21da, app-c1384707fc, app-e3b47169bc, app-e61a0b42ad and 8 more) |
| 4. The cheaper fix first | decided per need in Appendix B: rows `X2` (through its owner [`Cause`](Cause.md)) at tier stable (a member only where no rule, data, asset or app code serves the need) |