Skip to content

docs: align DVA error feedback with RFC 9457 - #89

Open
MYRhouma wants to merge 1 commit into
docs/dva-failure-modelfrom
docs/rfc9457-error-feedback
Open

docs: align DVA error feedback with RFC 9457#89
MYRhouma wants to merge 1 commit into
docs/dva-failure-modelfrom
docs/rfc9457-error-feedback

Conversation

@MYRhouma

@MYRhouma MYRhouma commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarifies which DVA component owns each documented failure and aligns the planned HTTP error contract with RFC 9457 Problem Details.

The failure hierarchy and Mermaid graph remain design references. The custom shared feedback-record proposal is removed so services can expose standard problem details without a universal internal DTO.

Review focus

  • Component ownership for every catalog entry
  • RFC 9457 type, title, status, detail, and instance mapping
  • Dashboard presentation guidance
  • Maintainable failure documentation

This PR is stacked on PR #86 and is documentation-only.

CC @bzp99

@MYRhouma
MYRhouma force-pushed the docs/rfc9457-error-feedback branch from a28cc66 to 541bf36 Compare September 8, 2026 01:39
@MYRhouma
MYRhouma marked this pull request as ready for review September 8, 2026 17:43
Copilot AI lite review requested due to automatic review settings September 8, 2026 17:43

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are documentation-only and appear internally consistent, complete, and aligned with the stated RFC 9457 Problem Details direction.

Pull request overview

Documentation update to the DVA failure model that clarifies which component is responsible for each failure and replaces the bespoke “feedback record” proposal with an RFC 9457 Problem Details–based HTTP error contract.

Changes:

  • Added an explicit Component owner to each failure catalog entry.
  • Replaced the “Proposed Feedback Record” section with guidance and an example for RFC 9457 application/problem+json responses.
  • Added dashboard/UI guidance for presenting title, detail, and links via type/instance.
File summaries
File Description
docs/failure-model.md Adds component ownership to failures and documents RFC 9457 Problem Details as the standard HTTP error shape.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants