Add two SuperDocs builds: multilingual family communication engine + background-check consent generator - #8
Open
rahuldhakshin wants to merge 1 commit into
Conversation
…ackground-check consent generator
rahuldhakshin
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two builds for the SuperDocs Round 2 take-home, both live-tested against the real SuperDocs API.
family-communication-engine — merges per-family fields deterministically, then makes a single-purpose SuperDocs translate call per language (Spanish, Arabic, Simplified Chinese). Found and fixed two real product-interaction issues: combining "merge fields AND translate" in one instruction left stale placeholders, and translated HTML carries no RTL markup (needed explicit dir="rtl" before PDF export). See its README and RECONCILIATION_REPORT.md for details.
background-check-consent-generator — produces a genuinely standalone FCRA disclosure, a separate signed authorization, and a separate rights notice, then verifies (not just asserts) the disclosure stays clean of waiver/liability/release language. See its README and RECONCILIATION_REPORT.md.