Repository navigation
docs: cleanup pass 3, architecture history, RFCs, e2e guides, operations - #63
Merged
Merged
Conversation
Removes 99 files: the phase 2 and phase 3 records and other history under docs/architecture, 25 of the 27 RFCs, all of docs/guides/e2e and all of docs/operations. RFC-0021 and RFC-0022 stay because code cites them by section. Content that had to survive moved to the site first, checked against the code: a class by class trace of one request and the points where it can stop (architecture/execution-pipeline.mdx), every table including policies, execution_intents and handbook_download_leads (storage/schema-reference.mdx), KMS troubleshooting rows and cautions (deployment/aws-kms-signing.mdx), and enforcement, the full scan check, the one step review script, a troubleshooting table and facts from the old developer guide (guides/policy-lifecycle-and-approvals.mdx). Citations of deleted records in CLAIMS, the handbook, ADR-0009, the connector docs, code comments, tutorials, tests, CI and .gitleaks.toml now name the record and say it is in git history, or point at the site page that replaced it. Co-Authored-By: Claude <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Pass 3 of the repository docs cleanup (pass 1 was PR #61, pass 2 was PR #62).
Removed (99 files)
execution-walkthrough.mdandDATABASE_SCHEMA_REFERENCE.md(both merged into the site first, see below)..mfile.Exception, as decided:
docs/rfcs/RFC-0021-Refusal-Record.mdanddocs/rfcs/RFC-0022-Challenge-Record.mdare kept. Code cites them by section (for examplepackages/shared/src/domain/challenge-record.ts, "RFC-0022 § Proposal 3"), a storage test uses the path as data, and CLAIMS 3.11 cites RFC-0021.Merged into the site first, checked against the code
architecture/execution-pipeline.mdx: a class by class trace of onePOST /executeand a table of every point where it can stop. It is written from today'sRuntimeEngine,ExecutionGateway,ExecutionControlServiceandSessionCredentialSecureConnector, not copied from the old walkthrough, which still named Razorpay.storage/schema-reference.mdx: now the single schema reference, with every table's columns and migrations. It adds three tables neither copy had (policies,execution_intents,handbook_download_leads) and states the correct count of 31 migrations. It also drops the stale claim that no policy had been approved.deployment/aws-kms-signing.mdx: troubleshooting rows for a missing gateway key file, signing and verification using different keys, and a cross service 500, plus a short "Keep in mind" list.guides/policy-lifecycle-and-approvals.mdx: when enforcement is on, the full scan check, the one step review script (with a warning thatrefresh-approved-policy-content.tsholds both keys in one process), a troubleshooting table and a "Good to know" list.References repointed
Citations of deleted records in CLAIMS, handbook chapters, ADR-0009, the connector docs, code comments in
packages/approval,packages/api,packages/sharedandpackages/storage, tutorials 95, 104, 113 to 115 and 117, tests,ci.ymland.gitleaks.tomlnow name the record and say it is in git history, or link the site page that replaced it. The terminology guard and documentation reference tests drop the deleted files from their lists. The.gitleaks.tomlallowlist entry stays becausedocs/site/deployment/local.mdxstill uses that demo hash; only its comment changed.No runtime behavior changes: docs, comments, tests and CI lists only. The full pre commit check passed.
🤖 Generated with Claude Code