Full-text search

Find the useful passage.

Search words, quoted phrases, and exact IDs across the current corpus.

Search in

All meaningful words must match the same passage. Use quotes for a phrase, or OR for alternatives. English sources need English search terms; queries are not translated.

All words must match a publication's name, ID or path. To find a term inside a publication, choose Full text.

Search syntax and examples

By default, all meaningful words must match the same source passage, in its text or titles. Matching ignores letter case. Ordinary word queries skip common English function words such as the, and and or; quotes keep a phrase, and uppercase operators control matching.

ExampleWhat it does
controlled variationRequires both meaningful words; their order may differ.
"controlled variation"Requires adjacent words in that order.
SYSE.24:4Prioritizes the exact named section. Pattern IDs also work.
engineering OR managementMatches either alternative. Write OR and AND in uppercase.
engineering AND (research OR management)Requires engineering together with either grouped alternative.
engineering -managementExcludes passages that match management.
title:"controlled variation"
body:"controlled variation"
Restricts the phrase to section/publication titles, or to source text. A field prefix applies to the following term or phrase.
"controlled variation"~1Allows one intervening word in the phrase.
"controlled vari"*Requires adjacent words, with the last word as a prefix.
engineering^2 OR managementGives engineering matches more ranking weight.

The Publication, Suite and Type filters narrow the same query. Results are source passages, not generated answers. Search does not translate, expand synonyms or automatically correct spelling. For a task expressed in another language, try English terms and read the context. Press / to focus the search field.

Refine query and filters
Full-text results: 1–15 of 64 matching passagesHeadings and contents · All publications · All suites · All kinds

B.3:4.7 - Leave domain obligations with their patterns

In B.3 - Is This Claim Supported for This Use? — Trust and Assurance Calculus

B.3 evaluates an assurance claim. It does not define safety duties, access rules, responsibility, affected-party disclosure, contest, redress, people or team status, resource allocation, release authority, or controlled action. Cite each applicable rule as a…

Read sectionOriginal sourcelines 47019–47024

B.3.4:4.3 - Treat epistemic debt as an optional planning indicator

In B.3.4 - Can Earlier Evidence Still Support This Use? — Evidence Decay and Epistemic Debt

… fits on its own. A count suffices when the question asks only how many obligations are overdue. Elapsed days can contribute to a justified priority rule or deterioration model. B.3.4 supplies no default rate, sum or automatic level downgrade. A planning count…

Read sectionOriginal sourcelines 47358–47365

B.3:4.10 - Use Working-Model declarations only for what they state

In B.3 - Is This Claim Supported for This Use? — Trust and Assurance Calculus

B.3:4.10 - Use Working-Model declarations only for what they state An E.14 Working-Model assertion may contribute its declared validation posture and grounding links. A postulate needs the empirical basis required by the assurance use; an inferential claim…

Read sectionOriginal sourcelines 47039–47042

B.3:4.8 - Preserve time, currentness, and design/run distinctions

In B.3 - Is This Claim Supported for This Use? — Trust and Assurance Calculus

B.3:4.8 - Preserve time, currentness, and design/run distinctions State the window only when time changes the assurance conclusion. Monitoring, drift, incidents, evidence refresh, version change, policy change, gate change, or a newly discovered defeater can…

Read sectionOriginal sourcelines 47025–47030