features

The final dataset: one capability statement per row, each with a verbatim excerpt of the archived documentation it rests on. This is release/features.csv.

Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University

form
user-action = 'The system lets …'; automation = 'The system automatically …'.
found_by
Which blind run's wording was kept (the other run may also have found it), or verifier/adjudicator for added capabilities.
verification
confirmed by the verifier; corrected (reworded); or added (missed by both runs).
pipeline_id
Link to the full pipeline record of this statement.
source_sha256
sha256 of the archived plain text the excerpt was checked against.
audited
1 if the row is in the 150-row blind audit sample.
audit_correct
Blind auditor's overall verdict (1 = acceptable as is).

1 row where pipeline_id = "F2-043-A108" and verification = "confirmed" sorted by feature_id

✎ View and edit SQL

This data as json, CSV (advanced)

verification 1

  • confirmed · 1 ✖

found_by 1

form 1

audit_correct 1

feature_id ▼ app_id statement form excerpt source_url source_file source_sha256 found_by found_by_runs verification pipeline_id audited audit_correct audit_note
F2-043-S103 ServiceNow IT Service Management F2-043 The system automatically creates an unauthorized change request and sends it for approval when an unplanned CI change occurs during an emergency change automation an unauthorized change request is created and sent for approvals https://www.servicenow.com/docs/api/khub/maps/eH2O6EPUpf09wX0~2cZBFg/topics/G1HoWNWZo0UNBvhOtETNEg/content 17.txt cd14fc97c0fb3bc06bd530582778b691b1354e859bb2599acce4743045798b53 extract-a both confirmed The system automatically creates an unauthorized change request and sends it for approval when an unplanned CI change occurs during an emergency change F2-043-A108 1.0 1.0 Emergency-change/unplanned-CI condition comes from surrounding sentence.

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [features] ([feature_id] TEXT PRIMARY KEY, [app_id] TEXT, [statement] TEXT, [form] TEXT, [excerpt] TEXT, [source_url] TEXT, [source_file] TEXT, [source_sha256] TEXT, [found_by] TEXT, [found_by_runs] TEXT, [verification] TEXT, [pipeline_id] TEXT, [audited] REAL, [audit_correct] REAL, [audit_note] TEXT, FOREIGN KEY ([app_id]) REFERENCES apps(app_id), FOREIGN KEY ([pipeline_id]) REFERENCES candidates(candidate_id));
CREATE INDEX [idx_features_app_id] ON [features]([app_id]);
CREATE INDEX [idx_features_verification] ON [features]([verification]);
CREATE INDEX [idx_features_form] ON [features]([form]);
CREATE INDEX [idx_features_found_by] ON [features]([found_by]);