Datasets:

jgalego
/

reqlint-real

id stringlengths 11 27	text stringlengths 40 372	defects listlengths 0 4	doubtful bool 2 classes	note stringlengths 13 247	source stringlengths 47 113	url stringlengths 41 109	license stringclasses 2 values
cfe-ces1001	Upon receipt of a Command, the cFE shall generate a NO-OP event message.	[]	false	Single active shall with a defined trigger and response.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1001	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1002	Upon receipt of a valid Command, the cFE shall increment a valid Command counter.	[]	false	Single active shall, one measurable response.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1002	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1003	Upon receipt of an invalid Command, the cFE shall increment the invalid Command counter and generate an event message.	[ "compound" ]	false	compound: increment the counter and generate an event message are two responses.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1003	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1004	Upon receipt of a Command, the cFE shall set to zero the valid Command counter and invalid Command counter.	[]	false	One action (set to zero) on two counters; a reviewer could call it compound. Review: One action on two objects is not compound (rule 1).	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1004	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1005-4	If the Command specified Application is already defined and executing, then the cFE shall reject the Command, increment the invalid Command counter and generate an event message.	[ "compound" ]	false	compound: reject, increment and generate are three responses.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1005.4	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1014	The cFE shall maintain an Executive Services System Log which contains a series of ASCII text strings describing significant events or errors.	[ "vague" ]	false	vague: 'significant events' has no criterion.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1014	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1316-2	If the Request Specified Critical Data Store does not exist, then the data shall not be copied.	[ "passive" ]	false	passive: 'shall not be copied' does not say what must not copy it.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1316.2	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1328-1	The cFE shall calculate a Data Integrity Value for the Request specified Critical Data Store and store it.	[ "compound", "pronoun" ]	true	compound: calculate and store; pronoun: 'it' most likely means the Data Integrity Value but could be read as the Critical Data Store.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1328.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1514	Upon a Processor Reset, the cFE shall preserve the contents of the Critical Data Store.	[]	false	Single active shall with a defined trigger.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1514	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1515-1	If the creation of the operating system object fails, the cFE shall perform a `<PLATFORM_DEFINED>` response.	[]	true	<PLATFORM_DEFINED> is a configuration parameter, not a TBD placeholder; a reviewer could still treat the unspecified response as tbd.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1515.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ces1709	If the cFE Core goes through `<PLATFORM_DEFINED>` Maximum Processor Resets, the cFE shall initiate a Power-On Reset of the cFE.	[]	false	Threshold is a platform configuration value; single active shall.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cES1709	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-cevs3103-6	The requester shall be able to specify the Application ID to be used in the Event Message.	[]	false	Single shall with a clear actor (the requester).	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cEVS3103.6	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-cevs3220	The cFE shall suppress event messages from an application that exceed a pre-defined rate.	[]	true	pronoun: 'that exceed' can refer to the messages or to the application; the 'pre-defined rate' is not given here. Review: 'that exceed' agrees with 'messages', so the referent is clear; 'pre-defined rate' points to a configured value (rules 2, 6).	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cEVS3220	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-csb4305-1	The cFE shall limit the number of messages of a particular Message ID that can be sent to an Application's Pipe.	[ "vague" ]	true	vague: says to limit the number of messages but gives no limit or where it is set.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cSB4305.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-csb4307	Upon receipt of a Request to receive a SB Message from a Pipe with a pending timeout, the cFE shall suspend execution of the Application until a SB Message is present on the Pipe or the timeout has expired.	[]	false	Single shall; 'or' gives the two end conditions of one response.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cSB4307	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6000-2	If the number of data bytes contained in the file is greater than the maximum size of the table, the load shall be aborted and an event message shall be generated.	[ "compound", "passive" ]	false	compound: two shall clauses; passive: 'shall be aborted', 'shall be generated' with no agent.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6000.2	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6302-1	If the Request specified File contains more data than the size of the Request specified Table, the Table Image will not be initialized and an Event Message shall be generated.	[ "compound", "passive", "weak_verb" ]	true	compound: two main clauses; passive: no agent; weak_verb: the first clause uses 'will not be initialized' rather than shall.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6302.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6308	Upon receipt of Request, the cFE shall update the request specified Table if a load is pending and it is unlocked.	[ "pronoun" ]	true	pronoun: 'it is unlocked' can refer to the Table or to the load.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6308	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6308-1	If a Table is locked when an update Request is made, an appropriate error code shall be returned to the calling Application and the update shall not occur.	[ "compound", "passive", "vague" ]	false	compound: two shall clauses; passive: 'shall be returned' with no agent; vague: 'appropriate error code'.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6308.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6500	Upon a Power-on Reset all Table resources shall be freed.	[ "passive" ]	false	passive: 'shall be freed' with no agent.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6500	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctbl6003-1-2	If a Table Validation Function does not exist for the specified Table, the Table shall be considered valid.	[ "passive" ]	false	passive: 'shall be considered valid' with no agent.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTBL6003.1.2	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctime2012-1	The cFE shall propagate time internally when set to ignore external time updates.	[]	false	Single active shall with a stated condition.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTIME2012.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctime2314	Upon receipt of a Request, the cFE shall provide the requested time value in the following format: `yyyy-ddd-hh:mm:ss.xxxxx\0`	[]	false	Single shall with an exact output format.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTIME2314	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
cfe-ctime2502-1	If the critical data store is not valid, all of the time elements shall be initialized in the same fashion as following a power-on reset.	[ "passive" ]	false	passive: 'shall be initialized' with no agent.	NASA cFE Functional Requirements (docs/cFE_FunctionalRequirements.csv), cTIME2502.1	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0
npr-7150-2d-swe-004	The NASA OCE shall periodically benchmark each Center’s software engineering capability against requirements in this directive.	[ "vague" ]	false	vague: 'periodically' gives no frequency.	NPR 7150.2D NASA Software Engineering Requirements, para 2.1.1.2 [SWE-004], p. 11	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-005	Center Director, or designee, shall establish, document, execute, and maintain software processes per the requirements in this directive.	[ "compound" ]	false	compound: establish, document, execute and maintain are four responses.	NPR 7150.2D NASA Software Engineering Requirements, para 2.1.5.3 [SWE-005], p. 12	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-2-1-5-9	Center Director, or designee, will maintain and implement software training to advance its in-house software engineering capabilities.	[ "compound", "pronoun", "weak_verb" ]	true	weak_verb: 'will'; compound: maintain and implement; pronoun: 'its' could mean the Center or the Center Director.	NPR 7150.2D NASA Software Engineering Requirements, para 2.1.5.9, p. 13	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-2-1-3-2	The NASA OCIO SAISO will participate in any software development reviews, as needed.	[ "escape", "weak_verb" ]	false	weak_verb: 'will'; escape: 'as needed'.	NPR 7150.2D NASA Software Engineering Requirements, para 2.1.3.2, p. 12	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-033	The project manager shall assess options for software acquisition versus development.	[]	false	Single active shall with a named actor.	NPR 7150.2D NASA Software Engineering Requirements, para 3.1.2 [SWE-033], p. 20	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-042	The project manager shall require the software developer(s) to provide NASA with electronic access to the source code developed for the project in a modifiable format.	[]	false	Single active shall with a named actor.	NPR 7150.2D NASA Software Engineering Requirements, para 3.1.10 [SWE-042], p. 21	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-018	The project manager shall regularly hold reviews of software schedule activities, status, performance metrics, and assessment/analysis results with the project stakeholders and track issues to resolution.	[ "compound", "vague" ]	false	vague: 'regularly'; compound: hold reviews and track issues.	NPR 7150.2D NASA Software Engineering Requirements, para 3.3.2 [SWE-018], p. 24	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-020	The project manager shall classify each system and subsystem containing software in accordance with the highest applicable software classification definitions for Classes A, B, C, D, E, and F software in Appendix D.	[]	false	Single active shall; criteria are referenced in Appendix D.	NPR 7150.2D NASA Software Engineering Requirements, para 3.5.1 [SWE-020], p. 24	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-178	If software IV&V is performed on a project, the project manager shall ensure that IV&V is provided access to development artifacts, products, source code, and data required to perform the IV&V analysis efficiently and effectively.	[ "vague" ]	false	vague: 'efficiently and effectively'.	NPR 7150.2D NASA Software Engineering Requirements, para 3.6.4 [SWE-178], p. 25	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-219	If a project has safety-critical software, the project manager shall ensure that there is 100 percent code test coverage using the Modified Condition/Decision Coverage (MC/DC) criterion for all identified safety-critical software components.	[]	false	Measurable: 100 percent MC/DC coverage.	NPR 7150.2D NASA Software Engineering Requirements, para 3.7.4 [SWE-219], p. 26	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-220	If a project has safety-critical software, the project manager shall ensure all identified safety-critical software components have a cyclomatic complexity value of 15 or lower. Any exceedance shall be reviewed and waived with rationale by the project manager or technical approval authority.	[ "compound", "passive" ]	false	compound: two shall sentences; the second names its agent so it is not passive. Review: Added passive: 'shall be reviewed and waived' names no actor.	NPR 7150.2D NASA Software Engineering Requirements, para 3.7.5 [SWE-220], p. 27	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-066	The project manager shall test the software against its requirements.	[]	false	Single active shall; 'its' clearly means the software.	NPR 7150.2D NASA Software Engineering Requirements, para 4.5.3 [SWE-066], p. 35	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-094	The project manager shall provide access to the software measurement data, measurement analyses, and software development status as requested to the sponsoring Mission Directorate, the NASA Chief Engineer, the Center Technical Authorities, HQ SMA, and other organizations as appropriate.	[ "escape" ]	false	escape: 'as appropriate' leaves the recipient list open.	NPR 7150.2D NASA Software Engineering Requirements, para 5.4.4 [SWE-094], p. 42	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-202	The project manager shall define and implement clear software severity levels for all software non-conformances (including tools, COTS, GOTS, MOTS, OSS, reused software components, and applicable ground systems).	[ "compound", "vague" ]	false	vague: 'clear' severity levels; compound: define and implement.	NPR 7150.2D NASA Software Engineering Requirements, para 5.5.2 [SWE-202], p. 42	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
npr-7150-2d-swe-073	The project manager shall validate the software system on the targeted platform or high-fidelity simulation.	[ "vague" ]	true	vague: 'high-fidelity' has no criterion; some reviewers treat it as a recognised term.	NPR 7150.2D NASA Software Engineering Requirements, para 4.5.8 [SWE-073], p. 36	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	public-domain (US gov work)
cfr-49-236-1	As required for maintenance, plans shall be kept at all interlockings, automatic signals and controlled points.	[ "escape", "passive" ]	false	escape: 'As required'; passive: 'shall be kept' with no agent.	49 CFR § 236.1 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.1	public-domain (US gov work)
cfr-49-236-4	The normal functioning of any device shall not be interfered with in testing or otherwise without first taking measures to provide for safety of train operation which depends on normal functioning of such device.	[ "passive", "vague" ]	true	passive: 'shall not be interfered with' with no agent; vague: 'normal functioning' (may be read as defined by the device design).	49 CFR § 236.4 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.4	public-domain (US gov work)
cfr-49-236-10	Electric locks on new installations and new electric locks applied to existing installations shall be of the forced drop type.	[]	false	Single shall stating a type; 'be of' is not passive.	49 CFR § 236.10 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.10	public-domain (US gov work)
cfr-49-236-11	When any component of a signal system, the proper functioning of which is essential to the safety of train operation, fails to perform its intended signaling function or is not in correspondence with known operating conditions, the cause shall be determined and the faulty component adjusted, repaired or replaced withou...	[ "compound", "passive", "vague" ]	false	compound: determine the cause and adjust, repair or replace; passive: no agent; vague: 'without undue delay'.	49 CFR § 236.11 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.11	public-domain (US gov work)
cfr-49-236-21	Each roadway signal shall be positioned and aligned so that its aspects can be clearly associated with the track it governs.	[ "compound", "passive", "vague" ]	true	passive: 'shall be positioned and aligned' with no agent; vague: 'clearly associated'; positioned and aligned could also count as compound. Review: Added compound: positioned and aligned are checked separately (rule 1).	49 CFR § 236.21 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.21	public-domain (US gov work)
cfr-49-236-23f	The absence of a qualifying appurtenance, the failure of a lamp in a light signal, or a false restrictive position of an arm of a semaphore signal shall not cause the display of a less restrictive aspect than intended.	[]	false	Single shall not with a defined failure set.	49 CFR § 236.23(f) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.23	public-domain (US gov work)
cfr-49-236-53	At grade crossing with an electric railroad where foreign current is present, the electric energy for noncoded direct current track circuit shall feed away from the crossing.	[]	false	Single shall with a stated condition.	49 CFR § 236.53 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.53	public-domain (US gov work)
cfr-49-236-73	Open-wire transmission line operating at voltage of 750 volts or more shall be placed not less than 4 feet above the nearest crossarm carrying signal or communication circuits.	[ "passive" ]	false	passive: 'shall be placed' with no agent; values have units.	49 CFR § 236.73 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.73	public-domain (US gov work)
cfr-49-236-108b	Then insulation resistance of wire or cable is found to be less than 500,000 ohms, prompt action shall be taken to repair or replace the defective wire or cable and until such defective wire or cable is replaced, insulation resistance test shall be made annually.	[ "compound", "passive", "vague" ]	false	compound: two shall clauses; passive: 'shall be taken', 'shall be made'; vague: 'prompt action'. Source typo 'Then' kept.	49 CFR § 236.108(b) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.108	public-domain (US gov work)
cfr-49-236-18b	Within 30 months of the completion of the software management control plan, each railroad shall have fully implemented such plan.	[]	false	Single shall with a deadline.	49 CFR § 236.18(b) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.18	public-domain (US gov work)
cfr-49-236-109	The timing shall be maintained at not less than 90 percent of the predetermined time interval, which shall be shown on the plans or marked on the time release, timing relay, or timing device.	[ "compound", "passive" ]	false	compound: maintained and shown/marked are two shall clauses; passive: no agent.	49 CFR § 236.109 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-236.109	public-domain (US gov work)
cfr-14-25-1302d	To the extent practicable, installed equipment must incorporate means to enable the flightcrew to manage errors resulting from the kinds of flightcrew interactions with the equipment that can be reasonably expected in service.	[ "escape", "vague" ]	true	escape: 'To the extent practicable'; vague: 'reasonably expected' (could be read as an accepted regulatory standard).	14 CFR § 25.1302(d) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1302	public-domain (US gov work)
cfr-14-25-1303c1	The speed warning device must give effective aural warning (differing distinctively from aural warnings used for other purposes) to the pilots, whenever the speed exceeds VMO plus 6 knots or MMO + 0.01.	[ "vague" ]	false	vague: 'effective' and 'differing distinctively'; thresholds are given.	14 CFR § 25.1303(c)(1) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1303	public-domain (US gov work)
cfr-14-25-1309b2	Each hazardous failure condition must be extremely remote.	[]	true	'Extremely remote' is a defined probability class in FAA guidance; without that context a reviewer might call it vague.	14 CFR § 25.1309(b)(2) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1309	public-domain (US gov work)
cfr-14-25-1309b4	Each significant latent failure must be eliminated as far as practical, or, if not practical to eliminate, the latency of the significant latent failure must be minimized.	[ "compound", "escape", "passive", "vague" ]	true	escape: 'as far as practical'; passive: 'be eliminated', 'be minimized' with no agent; vague: 'minimized'; compound: two must clauses. 'Significant latent failure' is a defined term.	14 CFR § 25.1309(b)(4) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1309	public-domain (US gov work)
cfr-14-25-1309c	The airplane and systems must provide information concerning unsafe system operating conditions to the flightcrew to enable them to take appropriate corrective action in a timely manner.	[ "vague" ]	false	vague: 'appropriate corrective action', 'timely manner'.	14 CFR § 25.1309(c) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1309	public-domain (US gov work)
cfr-14-25-1309e	The applicant must establish certification maintenance requirements as necessary to prevent the development of the failure conditions described in paragraph (b) of this section.	[ "escape" ]	false	escape: 'as necessary'.	14 CFR § 25.1309(e) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1309	public-domain (US gov work)
cfr-14-25-1321d	Instrument panel vibration may not damage or impair the accuracy of any instrument.	[]	false	weak_verb: main verb uses 'may not'; in 14 CFR 1.3 'may not' is a prohibition, so a reviewer may treat it as mandatory. Review: 'may not' is a prohibition under 14 CFR 1.3, so not a weak verb (rule 3).	14 CFR § 25.1321(d) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1321	public-domain (US gov work)
cfr-14-25-1321e	If a visual indicator is provided to indicate malfunction of an instrument, it must be effective under all probable cockpit lighting conditions.	[ "pronoun", "vague" ]	true	vague: 'effective'; 'it' clearly refers to the indicator. Review: Added pronoun: 'it' can mean the indicator or the instrument.	14 CFR § 25.1321(e) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1321	public-domain (US gov work)
cfr-14-25-1357b	The protective and control devices in the generating system must be designed to de-energize and disconnect faulty power sources and power transmission equipment from their associated busses with sufficient rapidity to provide protection from hazardous over-voltage and other malfunctioning.	[ "compound", "passive", "vague" ]	false	passive: 'must be designed' with no agent; vague: 'sufficient rapidity'. Review: Added compound: de-energize and disconnect are separate actions (rule 1).	14 CFR § 25.1357(b) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1357	public-domain (US gov work)
cfr-14-25-1357d	Where fuses are used, there must be spare fuses for use in flight equal to at least 50% of the number of fuses of each rating required for complete circuit protection.	[]	false	Measurable: at least 50% of each rating.	14 CFR § 25.1357(d) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1357	public-domain (US gov work)
cfr-14-25-1383c	There must be a means to indicate to the pilots when the landing lights are extended.	[]	false	Single must, verifiable.	14 CFR § 25.1383(c) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1383	public-domain (US gov work)
cfr-14-25-1421	If a megaphone is installed, a restraining means must be provided that is capable of restraining the megaphone when it is subjected to the ultimate inertia forces specified in § 25.561(b)(3).	[ "passive" ]	false	passive: 'must be provided' with no agent; 'it' clearly means the megaphone.	14 CFR § 25.1421 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1421	public-domain (US gov work)
cfr-14-25-1433	There must be means, in addition to the normal pressure relief, to automatically relieve the pressure in the discharge lines from the vacuum air pump when the delivery temperature of the air becomes unsafe.	[ "vague" ]	true	vague: 'unsafe' delivery temperature has no value.	14 CFR § 25.1433 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1433	public-domain (US gov work)
cfr-14-25-1331a2	Each instrument must, in the event of the failure of one power source, be supplied by another power source.	[]	true	Passive form but the agent is named ('by another power source'), so not passive by the definition.	14 CFR § 25.1331(a)(2) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1331	public-domain (US gov work)
cfr-14-25-1322f	Use of the colors red, amber, and yellow on the flight deck for functions other than flightcrew alerting must be limited and must not adversely affect flightcrew alerting.	[ "compound", "passive", "vague" ]	false	compound: two must clauses; passive: 'must be limited' with no agent; vague: 'limited', 'adversely affect'.	14 CFR § 25.1322(f) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-14/section-25.1322	public-domain (US gov work)
cfr-10-50b-i-authority	The authority and duties of persons and organizations performing activities affecting the safety-related functions of structures, systems, and components shall be clearly established and delineated in writing.	[ "compound", "passive", "vague" ]	true	passive: no agent; vague: 'clearly'; compound: established and delineated (may be read as one action).	10 CFR Part 50 Appendix B, Criterion I (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-i-sufficient	The persons and organizations performing quality assurance functions shall have sufficient authority and organizational freedom to identify quality problems; to initiate, recommend, or provide solutions; and to verify implementation of solutions.	[ "compound", "vague" ]	true	vague: 'sufficient authority and organizational freedom'. Review: Added compound: authority and organizational freedom are separate properties (rule 1).	10 CFR Part 50 Appendix B, Criterion I (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-ii-earliest	The applicant shall establish at the earliest practicable time, consistent with the schedule for accomplishing the activities, a quality assurance program which complies with the requirements of this appendix.	[ "escape" ]	false	escape: 'at the earliest practicable time'.	10 CFR Part 50 Appendix B, Criterion II (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-ii-suitably	Activities affecting quality shall be accomplished under suitably controlled conditions.	[ "passive", "vague" ]	false	passive: 'shall be accomplished' with no agent; vague: 'suitably controlled'.	10 CFR Part 50 Appendix B, Criterion II (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-iii-verifying	The verifying or checking process shall be performed by individuals or groups other than those who performed the original design, but who may be from the same organization.	[]	false	Agent is named, so not passive; 'may' is in a subordinate clause.	10 CFR Part 50 Appendix B, Criterion III (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-iv-extent	To the extent necessary, procurement documents shall require contractors or subcontractors to provide a quality assurance program consistent with the pertinent provisions of this appendix.	[ "escape" ]	false	escape: 'To the extent necessary'.	10 CFR Part 50 Appendix B, Criterion IV (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-x-such	Such inspection shall be performed by individuals other than those who performed the activity being inspected.	[]	false	Agent is named; 'Such inspection' points to the previous sentence of the criterion.	10 CFR Part 50 Appendix B, Criterion X (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-x-where	Examinations, measurements, or tests of material or products processed shall be performed for each work operation where necessary to assure quality.	[ "escape", "passive" ]	false	escape: 'where necessary'; passive: 'shall be performed' with no agent.	10 CFR Part 50 Appendix B, Criterion X (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-xvii-records	Records shall be identifiable and retrievable.	[ "compound" ]	true	compound: two properties joined by 'and'; some reviewers would accept it as one.	10 CFR Part 50 Appendix B, Criterion XVII (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-10-50b-xviii-results	Audit results shall be documented and reviewed by management having responsibility in the area audited.	[ "compound" ]	false	compound: documented and reviewed; passive: 'documented' has no agent (the agent applies to 'reviewed'). Review: 'by management' covers both participles, so not passive (rule 4).	10 CFR Part 50 Appendix B, Criterion XVIII (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	public-domain (US gov work)
cfr-49-571-114-s5-1-2	For each vehicle type manufactured by a manufacturer, the manufacturer must provide at least 1,000 unique key combinations, or a number equal to the total number of the vehicles of that type manufactured by the manufacturer, whichever is less.	[]	false	Measurable count with a clear actor.	49 CFR § 571.114, S5.1.2 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-49-571-114-s5-1-3	Except as specified below, an audible warning to the vehicle operator must be activated whenever the key is in the starting system and the door located closest to the driver's designated seating position is opened.	[ "passive" ]	true	passive: 'must be activated' with no agent; 'Except as specified below' points to listed exceptions, so not labelled escape.	49 CFR § 571.114, S5.1.3 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-49-571-114-s5-2-2	Except as specified in S5.2.4, the vehicle must be designed such that the transmission or gear selection control cannot move from the “park” position, unless the key is in the starting system.	[ "passive" ]	true	passive: 'must be designed' with no agent; the design constraint itself is clear.	49 CFR § 571.114, S5.2.2 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-49-571-114-s5-2-5	When tested in accordance with S6.2.2, each vehicle must not move more than 150 mm on a 10 percent grade when the gear selection control is locked in “park.”	[]	false	Measurable: 150 mm on a 10 percent grade.	49 CFR § 571.114, S5.2.5 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-49-571-114-s5-3b	This system shall function in any starting system key position in which the transmission can be shifted out of “park.”	[]	false	'This system' refers to the system in the previous sentence; single shall.	49 CFR § 571.114, S5.3 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-49-571-114-s6-1-2	Except where specified otherwise, the test surface shall be level.	[ "escape" ]	true	escape: 'Except where specified otherwise'; 'level' has no tolerance, which some would label vague.	49 CFR § 571.114, S6.1.2 (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-49/section-571.114	public-domain (US gov work)
cfr-21-1020-30k	The leakage radiation from the diagnostic source assembly measured at a distance of 1 meter in any direction from the source shall not exceed 0.88 milligray (mGy) air kerma (vice 100 milliroentgen (mR) exposure) in 1 hour when the x-ray tube is operated at the leakage technique factors.	[]	false	Measurable limit with units and conditions.	21 CFR § 1020.30(k) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30l	The radiation emitted by a component other than the diagnostic source assembly shall not exceed an air kerma of 18 microGy (vice 2 mR exposure) in 1 hour at 5 cm from any accessible surface of the component when it is operated in an assembled x-ray system under any conditions for which it was designed.	[]	false	Measurable limit with units; 'it' clearly means the component.	21 CFR § 1020.30(l) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30o	On battery-powered generators, visual means shall be provided on the control panel to indicate whether the battery is in a state of charge adequate for proper operation.	[ "passive", "vague" ]	false	passive: 'shall be provided' with no agent; vague: 'adequate for proper operation'.	21 CFR § 1020.30(o) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30e1	In a similar manner, manufacturers of tube housing assemblies shall also inscribe or affix thereon the name of the manufacturer, model number, and serial number of the x-ray tube which the tube housing assembly incorporates.	[]	false	Single shall with a named actor; 'inscribe or affix' are alternatives.	21 CFR § 1020.30(e)(1) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30m2	A means of indicating which combination of additional filtration is in the x-ray beam shall be provided.	[ "passive" ]	false	passive: 'shall be provided' with no agent.	21 CFR § 1020.30(m)(2) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30d1	Completed reports must be submitted to the purchaser and, where applicable, to the State agency responsible for radiation protection within 15 days following completion of the assembly.	[ "escape", "passive" ]	true	passive: 'must be submitted' with no agent; escape: 'where applicable' (close to 'as appropriate').	21 CFR § 1020.30(d)(1) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
cfr-21-1020-30e-word	The word “model” or “type” shall appear as part of the manufacturer's required identification of certified x-ray components.	[]	false	Single shall, verifiable.	21 CFR § 1020.30(e) (eCFR, current as of 2026-09-29)	https://www.ecfr.gov/current/title-21/section-1020.30	public-domain (US gov work)
fda-sw-premarket-lifecycle	Sponsors should establish a software life cycle model that is appropriate for their product and organization, and meets the applicable regulatory requirements.	[ "vague", "weak_verb" ]	false	weak_verb: 'should'; vague: 'appropriate for their product and organization'.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 10	https://www.fda.gov/media/153781/download	public-domain (US gov work)
fda-sw-premarket-criteria	The acceptability criteria should be documented in the risk management plan before an initial risk evaluation is performed for the device software under review.	[ "passive", "weak_verb" ]	false	weak_verb: 'should'; passive: 'be documented' with no agent.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 19	https://www.fda.gov/media/153781/download	public-domain (US gov work)
fda-sw-premarket-srs	A singular SRS document or set of multiple SRS documents should be provided.	[ "passive", "weak_verb" ]	false	weak_verb: 'should'; passive: 'be provided' with no agent.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 23	https://www.fda.gov/media/153781/download	public-domain (US gov work)
fda-sw-premarket-sds	The information presented in the SDS should be sufficient to ensure that the work performed by the software engineers who created the device software function was clear and unambiguous, with minimal ad hoc design decisions.	[ "vague", "weak_verb" ]	false	weak_verb: 'should'; vague: 'sufficient', 'minimal'.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 26	https://www.fda.gov/media/153781/download	public-domain (US gov work)
fda-sw-premarket-summary	The summary description should include the software version tested and the overall pass/fail test results for all test protocols (i.e., collection of test procedures for specific software functionality) executed.	[ "weak_verb" ]	false	weak_verb: 'should'.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 29	https://www.fda.gov/media/153781/download	public-domain (US gov work)
fda-sw-premarket-anomalies	Where appropriate, a sponsor should communicate to end users any mitigations or possible work-arounds for unresolved anomalies to assist in the proper operation of the device to fulfill its intended use.	[ "escape", "weak_verb" ]	false	weak_verb: 'should'; escape: 'Where appropriate'.	FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023), PDF p. 31	https://www.fda.gov/media/153781/download	public-domain (US gov work)
nasa-lcrns-3-0010	The Lunar Relay service shall comply with the interfaces specified in the LunaNet Interoperability Specification LNIS V.4 (ESC-LCRNS-SPEC-0015) per the compliance matrix in Appendix C.	[]	false	Single shall, verifiable against a referenced specification.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0010, PDF p. 19	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)
nasa-lcrns-3-0020	The Lunar Relay Service shall provide key operational support to lunar systems.	[ "vague" ]	false	vague: 'key operational support' is not defined in the statement.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0020, PDF p. 19	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)
nasa-lcrns-3-0090	The Lunar Relay Service shall provide nominal operational service Availability as shown in Table 3-1 for each of the IOC increments, averaged over a period of one Earth month.	[]	true	Statement is clean, but the Table 3-1 values it points to are all TBR.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0090, PDF p. 21	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)
nasa-lcrns-3-0130	The Lunar Relay Service shall provide LANS services with Geometric Dilution of Precision (GDOP) <6 (TBR) in the Service Volumes identified in Table 3-3.	[ "tbd" ]	false	tbd: '(TBR)' on the GDOP value; GDOP is dimensionless.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0130, PDF p. 24	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)
nasa-lcrns-3-0170	The Lunar Relay Service shall cover dynamic events such as lunar vehicle descent and ascent, lunar orbiting vehicles, and mobility surface vehicles and personnel.	[ "escape" ]	true	escape: 'such as' leaves the list open, close to 'including but not limited to'.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0170, PDF p. 25	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)
nasa-lcrns-3-0230	The Lunar Relay Service shall provide navigation services such that the NASA human spaceflight architecture on the lunar surface can meet a minimum of 24 hours of cumulative surface EVA time per crewmember per 7 Earth-day period during surface stays greater than or equal to 14 Earth-days.	[]	false	Measurable: 24 hours per crewmember per 7 Earth-day period.	NASA ESC-LCRNS-REQ-0090 Lunar Relay Services Requirements Document (SRD) Rev B w/DCN 001, LCRNS.3.0230, PDF p. 26	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	public-domain (US gov work)

End of preview. Expand in Data Studio

Real requirements, hand-labelled

Requirement statements from public-domain US government documents and Apache-2.0 NASA software, each labelled with the writing defects used by jgalego/reqlint-smollm3-3b: compound, escape, no_unit, passive, pronoun, tbd, vague, weak_verb. Labels were proposed with a written reason per row (note), then checked against the rules below; changes from that check are recorded in note after Review:. Rows a reasonable reviewer might still label differently have doubtful: true.

Evaluation only. Each row carries its own source, url and license; the compilation is released under Apache-2.0.

Labelling rules

A label applies to the statement's own text, judged by its main verb.

compound: two or more actions or properties that can be checked separately ("establish and maintain", "documented and reviewed", "recoverable and reusable"). One action on a list of objects is not compound.
vague: an undefined quality word where a value is needed ("high-fidelity", "unsafe", "minimized"). A term the governing document or framework defines is not vague ("extremely remote" in FAA system safety guidance).
weak_verb: judged by the source's drafting convention. "may not" in the CFR is a prohibition (14 CFR 1.3), so it is not weak. "will" where the source uses "shall" for requirements is weak, as is "should" in nonbinding FDA guidance.
passive: no actor named. A "by ..." phrase after coordinated participles names the actor for all of them.
escape: open-ended clauses and example lists ("as necessary", "where applicable", "such as", "etc."). An exception that points to a specific clause ("except as specified in S5.2.4") is not an escape; one that points nowhere ("except where specified otherwise") is.
tbd: placeholders in the statement itself (TBD, TBR). Configuration parameters such as <PLATFORM_DEFINED> and TBR values in a referenced table do not count.

Sources

Document	URL	Licence basis	Rows
NASA Core Flight Executive (cFE) functional requirements, `docs/cFE_FunctionalRequirements.csv` at commit 12cb84f	https://github.com/nasa/cFE/blob/12cb84fc3ef22e584d94dba571e0c4f9a59397cb/docs/cFE_FunctionalRequirements.csv	Apache-2.0 (repo LICENSE)	24
NASA Student Launch 2026 Handbook & Request for Proposal (MSFC-07-2025-G-677852)	https://www.nasa.gov/wp-content/uploads/2025/08/g-677852-2026-sli-handbook-508-aug-7-optimized.pdf	Public domain: NASA MSFC publication, 17 U.S.C. 105. No copyright notice.	19
NPR 7150.2D, NASA Software Engineering Requirements (2022)	https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7150_002D_/N_PR_7150_002D_.pdf	Public domain: NASA directive, 17 U.S.C. 105. No copyright notice.	15
ESC-LCRNS-REQ-0090, Lunar Relay Services Requirements Document (SRD), Rev B w/DCN 001	https://www.nasa.gov/wp-content/uploads/2025/08/lunar-relay-services-requirements-document-srd.pdf	Public domain: prepared and approved by NASA GSFC staff (signature page), 17 U.S.C. 105. No copyright notice.	15
14 CFR Part 25 Subpart F, Airworthiness Standards: Transport Category Airplanes, Equipment (FAA)	https://www.ecfr.gov/current/title-14/part-25/subpart-F	Public domain: federal regulation, 17 U.S.C. 105	15
49 CFR Part 236 Subpart A, Signal and Train Control Systems (FRA)	https://www.ecfr.gov/current/title-49/part-236/subpart-A	Public domain: federal regulation, 17 U.S.C. 105	11
10 CFR Part 50 Appendix B, Quality Assurance Criteria for Nuclear Power Plants (NRC)	https://www.ecfr.gov/current/title-10/part-50/appendix-Appendix%20B%20to%20Part%2050	Public domain: federal regulation, 17 U.S.C. 105	10
21 CFR 1020.30, Diagnostic x-ray systems and their major components (FDA)	https://www.ecfr.gov/current/title-21/section-1020.30	Public domain: federal regulation, 17 U.S.C. 105	7
49 CFR 571.114, FMVSS No. 114, Theft protection and rollaway prevention (NHTSA)	https://www.ecfr.gov/current/title-49/section-571.114	Public domain: federal regulation, 17 U.S.C. 105	6
FDA guidance, Content of Premarket Submissions for Device Software Functions (June 14, 2023)	https://www.fda.gov/media/153781/download	Public domain: FDA guidance, 17 U.S.C. 105. No copyright notice.	6

CFR text was taken from the eCFR on 2026-10-01 (titles current as of 2026-09-29). The eCFR is not an official legal edition of the CFR.

Caveats

The LCRNS PDF metadata names a GSFC support contractor (MTI Systems) as the file author. The document has no copyright notice and its signature page lists only NASA staff, so it is treated as a US government work.
The Student Launch handbook was laid out in InDesign and the layout may be contractor work. Only its text is used here, and the text carries no copyright notice.
The cFE source files carry the notice "Copyright (c) 2023 United States Government as represented by the Administrator of NASA. All Rights Reserved." together with the Apache-2.0 grant. The CSV has no header of its own, so the repo licence applies.
If you hold rights to any of these texts and want them removed, open a discussion on this repo and the rows will be taken down.
FDA guidance uses "should" by design (nonbinding recommendations). Those rows are labelled weak_verb by the taxonomy, not because the guidance is badly written.