Find the information you need.

Processing and mode: Source implemented with deterministic generation fallback; external generation service unverified

Assessed behavior and limits: PDF/DOC/DOCX file selection is not proof of content extraction; text-like files can supply text. Standards suggestions are presets, not authoritative compliance determinations.

Processing and mode: Source implemented browser file processing

Assessed behavior and limits: Separate from document report format buttons. Imported field completeness and provenance need acceptance tests.

Processing and mode: Derived client presentation over graph; live route HTTP200

Assessed behavior and limits: Metrics describe stored model records. They do not independently establish vessel safety, real verification or engineering maturity.

Processing and mode: Derived client rules plus optional external K service unverified

Assessed behavior and limits: One source defect can appear repeatedly across multiple dashboards; counts should not be summed across modules.

Processing and mode: Derived client analysis plus optional K service unverified

Assessed behavior and limits: Health is a modeled completeness/control score, not independent assurance or measured probability of failure.

Processing and mode: Source implemented graph-derived stage UI

Assessed behavior and limits: Stage completion relies on presence/status heuristics; formal authority and evidence quality must be verified separately.

Processing and mode: Source implemented visual projection

Assessed behavior and limits: Edges displayed are stored assertions; link existence does not prove engineering correctness.

Processing and mode: Source implemented projection catalogue

Assessed behavior and limits: Availability of view type is not proof all notation semantics, editing and exchange capabilities are complete.

Processing and mode: Source implemented graph traversal

Assessed behavior and limits: Distinct from digital-thread route. Empty or incorrect graph relationships directly affect results.

Processing and mode: Source implemented static ontology plus graph references; live bundle confirmed

Assessed behavior and limits: 36 NodeType declarations; some classes have no dedicated create/edit route. Declared fields differ from some canonical ontology field names.

Processing and mode: Source implemented rules; live bundle confirmed

Assessed behavior and limits: Rules are finite programmed checks; do not substitute for semantic engineering validation.

Processing and mode: Source implemented read/filter interface

Assessed behavior and limits: Displayed qualityScore can originate in seeded/imported data; assess consistency with recomputed analyzer scores.

Processing and mode: Source implemented graph mutations; live write persistence not exercised

Assessed behavior and limits: AI drafting and autosuggest need human review. Mutation rules and server enforcement are separate assessment topics.

Processing and mode: Source implemented heuristic/analysis presentation; external augmentation unverified

Assessed behavior and limits: A rewrite suggestion is an output proposal until explicitly applied to graph.

Processing and mode: Source implemented secondary routes; HTTP render not sampled individually

Assessed behavior and limits: Baseline labels and status are not evidence of immutable snapshot management or electronic approval.

Processing and mode: Source implemented graph projection; architecture bundle matched local output

Assessed behavior and limits: Operational narrative and system relationships are model descriptions rather than executed simulation.

Processing and mode: Source implemented graph writes; no write exercised

Assessed behavior and limits: UI draft quality, cross-domain defaults and validation require representative project testing.

Processing and mode: Source implemented UI and graph writes

Assessed behavior and limits: technicalSpec is free text; no demonstrated signal-level payload, units, rates, direction, timing or safe-state schema.

Processing and mode: Source implemented CRUD/derived analysis

Assessed behavior and limits: Risk numbers are ordinal 1–5 model inputs; residual score is not a measured risk reduction or validated prediction.

Processing and mode: Source implemented local-first graph creation

Assessed behavior and limits: A case row proves planned coverage only; it does not prove completed testing.

Processing and mode: Source implemented local-first graph mutation

Assessed behavior and limits: Evidence capture is text/reference oriented; no demonstrated raw measurement upload, instrument traceability, calibration or independent witness verification.

Processing and mode: Source implemented graph record creation; authority/identity service unverified

Assessed behavior and limits: Typing Signed by is not equivalent to cryptographic signature or authenticated approval authority.

Processing and mode: Source implemented model-derived checks and evidence records

Assessed behavior and limits: No proof of up-to-date licensed standards ingestion, clause interpretation, accredited review or regulatory acceptance.

Processing and mode: Source implemented graph model and calculations

Assessed behavior and limits: Not a financial ledger or ERP integration; actual cost values are modeled inputs unless independently sourced.

Processing and mode: Source implemented graph-derived schedule

Assessed behavior and limits: No demonstrated enterprise scheduler import, resource leveling, baseline comparison or full CPM calculation.

Processing and mode: Source implemented stored records

Assessed behavior and limits: Supplier names/amounts in sample are demonstration data, not independently verified quotations.

Processing and mode: Source implemented write path and lifecycle rules

Assessed behavior and limits: Approval status requires identity/authorization and authoritative persistence assessment; presence of AI impact text is not independent validation.

Processing and mode: Metadata/reference presentation and simulated sample add; PDF print path; non-PDF export success only

Assessed behavior and limits: Add sample reference cycles canned names; no file picker/upload. Word/Excel/CSV/JSON export buttons do not create a file in inspected source.

Processing and mode: Graph metadata presentation, not demonstrated report assembly

Assessed behavior and limits: The preview is description plus linked source objects. Stated page counts are data fields, not generated pagination evidence.

Processing and mode: Source implemented local decision workflow; live PRISM/backend capabilities separately unverified

Assessed behavior and limits: Model output and citations are not automatically verified evidence. Human approval and research verification are distinct inputs.

Processing and mode: Source implemented stored graph records

Assessed behavior and limits: Issue closure state should be backed by linked verified resolution evidence.

Processing and mode: Source implemented graph records

Assessed behavior and limits: Confidence is asserted metadata unless a method, evidence and reviewer are supplied.

Processing and mode: Client analysis/simulated-agent presentation plus optional K service unverified

Assessed behavior and limits: Multiple displayed reviewers do not establish independent model calls, independent engineering review or accreditation.

Processing and mode: Client-derived rules with page-local overrides; external K unverified

Assessed behavior and limits: Changing checklist override changes display state, not necessarily the underlying controlled artifact or persistent evidence.

Processing and mode: Source implemented deterministic graph-impact model plus optional K response unverified

Assessed behavior and limits: Estimates are heuristics over stored links, not CFD/FEA, schedule simulation or validated cost engineering.

Processing and mode: Client authored study with local recomputation; genuine CSV download implemented

Assessed behavior and limits: Generate reveals preset graph-appropriate content. Sliders do not demonstrate option discovery, external research or persistent design decision.

Processing and mode: Source implemented heuristic predictions plus optional external K service unverified

Assessed behavior and limits: Prediction labels and confidence percentages lack demonstrated calibration or external outcome validation.

Processing and mode: Stored/generated recommendation presentation

Assessed behavior and limits: Some recommendations are hard-coded seed records with modelUsed/promptVersion labels; these labels do not prove a model ran.

Processing and mode: Derived client summary plus optional external K unverified

Assessed behavior and limits: A synthesized brief inherits every uncertainty and stale/missing source record in the graph.

Processing and mode: Source implemented graph-memory view plus optional K unverified

Assessed behavior and limits: Local view of project records is not proof of enterprise cross-project learning or validated retrieval over external documents.

Processing and mode: Deterministic client extraction; graph conversion implemented

Assessed behavior and limits: Marine project falls through to island-water-plant sample/domain label. No audio recording, transcription or live meeting connection demonstrated.

Processing and mode: Source implemented client+API path; live service outcome separately unverified

Assessed behavior and limits: Prompt, graph data and external model traffic are information outputs to service; exact provider deployment/retention not established by UI.

Processing and mode: Local query interpretation/evaluation implemented; relevant live bundle matched local output

Assessed behavior and limits: Query coverage is bounded by supported grammar/intents; unknown requests should produce uncertainty rather than invented results.

Processing and mode: Source implemented graph algorithms

Assessed behavior and limits: Computed paths establish graph connectivity only, not physical causality.

Processing and mode: Client context build implemented; external AI request unverified

Assessed behavior and limits: Context quality score is not groundedness proof; leakage/tenant scope and evidence completeness must be tested separately.

Processing and mode: Source implemented graph-derived dashboard

Assessed behavior and limits: Different route and scoring basis from thread; align definitions to avoid contradictory coverage claims.

Processing and mode: Source implemented health analysis; historical/benchmark provenance requires verification

Assessed behavior and limits: Presence of mock scenario files warrants checking runtime selection; do not treat benchmark/trend values as measured longitudinal data without provenance.

Processing and mode: Source implemented diagram generation/export

Assessed behavior and limits: SVG/PNG paths create artifacts, unlike non-PDF document buttons. Not proof of full native SysML/MBSE interchange or executable model semantics.

Processing and mode: Local browser storage ring buffer; guest visibility restricted in source

Assessed behavior and limits: Not equivalent to immutable central security audit, server access log or cross-device forensic trail.

Processing and mode: Source implemented capability catalogue

Assessed behavior and limits: An Active label alone is not runtime evidence of an independently operating agent or successful model/tool execution.

Processing and mode: Modelled only; explicitly not connected to live telemetry

Assessed behavior and limits: No streaming values, historical ingestion or live device connection established; future operations claim is prospective.

Processing and mode: Source implemented read-only settings and browser JSON download.

Assessed behavior and limits: Project details must be changed through re-import of an updated master file; this settings page has no edit or reset control.

Processing and mode: Simulated local invite state; no email/network call in page

Assessed behavior and limits: Send invite does not demonstrate invitation delivery or access provisioning; people list is derived from Stakeholder nodes.

Processing and mode: Source implemented role catalogue; authorization enforcement separately assessed

Assessed behavior and limits: Sixteen roles in schema. Displayed role selection is not a substitute for server-enforced permissions.

Processing and mode: Explicitly simulated in preview; no OAuth credentials exchanged

Assessed behavior and limits: Do not count this page as working Slack/Jira/DevOps integration or proof every listed core datastore is deployed.

Processing and mode: Source implemented graph-derived audit UI

Assessed behavior and limits: Audit array provenance/integrity is distinct from append-only server audit and signed change evidence.

Processing and mode: Client rule checks and some graph write-back; secondary routes source inspected

Assessed behavior and limits: Some gates equate approved-count thresholds with baselined readiness; sensor count with telemetry configuration. These proxies need explicit stronger acceptance rules.

Processing and mode: Local route/API source present; not included in 45 live route sampling and service unverified

Assessed behavior and limits: Treat as repository capability until deployed route and backend are validated.

Processing and mode: Client/auth source present; no credentials submitted in assessment

Assessed behavior and limits: Authentication and role authorization are separate; assessment did not create an account or perform privileged mutations.

Processing and mode: Live bundle confirms loadOverride/saveOverride, Supabase graph loader, mutation guards and API pathways; service success not established by presence

Assessed behavior and limits: Separate model information leaving browser for AI/cloud services from UI outputs. Exact configured backend, tenancy, retention, backups and network behavior require runtime evidence.