103 lines
2.8 KiB
Markdown
103 lines
2.8 KiB
Markdown
# 10. Technology Validation Sources
|
|
|
|
Validation date: **2026-02-26**
|
|
|
|
This proposal uses current official documentation (and release notes where relevant) for each major recommended technology.
|
|
|
|
## 1. OpenClaw
|
|
|
|
- Docs home: https://docs.openclaw.ai/
|
|
- Plugin development/hooks: https://docs.openclaw.ai/guide/developers/plugins/overview/
|
|
- Browser tool docs: https://docs.openclaw.ai/guide/tools/browser/
|
|
- OpenClaw GitHub releases/readme: https://github.com/openclawai/openclaw
|
|
|
|
Used for:
|
|
- hook names and plugin lifecycle
|
|
- browser capabilities and profile modes
|
|
- upstream release/update model
|
|
|
|
## 2. Next.js
|
|
|
|
- Official docs: https://nextjs.org/docs
|
|
- Release notes: https://nextjs.org/blog
|
|
|
|
Used for:
|
|
- app router patterns
|
|
- deployment/runtime guidance
|
|
- version-aware migration planning
|
|
|
|
## 3. Prisma
|
|
|
|
- Official docs: https://www.prisma.io/docs
|
|
- ORM release notes: https://github.com/prisma/prisma/releases
|
|
|
|
Used for:
|
|
- schema/migration guidance
|
|
- Prisma Client behavior and deployment practices
|
|
|
|
## 4. React Native + Expo
|
|
|
|
- React Native docs: https://reactnative.dev/docs/getting-started
|
|
- React Native releases: https://github.com/facebook/react-native/releases
|
|
- Expo docs: https://docs.expo.dev/
|
|
- Expo SDK changelog: https://expo.dev/changelog
|
|
|
|
Used for:
|
|
- mobile stack decision
|
|
- push notification and build pipeline planning
|
|
|
|
## 5. Flutter (evaluated alternative)
|
|
|
|
- Flutter docs: https://docs.flutter.dev/
|
|
- Flutter releases: https://github.com/flutter/flutter/releases
|
|
|
|
Used for:
|
|
- alternative comparison for mobile stack decision
|
|
|
|
## 6. Playwright
|
|
|
|
- Official docs: https://playwright.dev/docs/intro
|
|
- Release notes: https://playwright.dev/docs/release-notes
|
|
|
|
Used for:
|
|
- browser automation fallback strategy
|
|
- testing and scenario migration approach
|
|
|
|
## 7. SQLite
|
|
|
|
- SQLite docs: https://www.sqlite.org/docs.html
|
|
- SQLite file format/security references: https://www.sqlite.org/fileformat.html
|
|
|
|
Used for:
|
|
- tenant-local vault, approval cache, and usage bucket storage design
|
|
|
|
## 8. Stripe
|
|
|
|
- Stripe API docs: https://docs.stripe.com/api
|
|
- Usage-based billing/meter events: https://docs.stripe.com/billing/subscriptions/usage-based
|
|
|
|
Used for:
|
|
- overage billing architecture
|
|
- usage ingestion and invoice flow design
|
|
|
|
## 9. Gitea Actions / Act Runner
|
|
|
|
- Gitea Actions docs: https://docs.gitea.com/usage/actions/overview
|
|
- Act runner docs: https://docs.gitea.com/usage/actions/act-runner
|
|
|
|
Used for:
|
|
- CI/CD workflow strategy
|
|
- runner security and deployment pipeline design
|
|
|
|
## 10. Additional Provider References
|
|
|
|
- Netcup API context (existing integration baseline): https://www.netcup.com/en
|
|
- Hetzner Cloud docs (overflow strategy): https://docs.hetzner.cloud/
|
|
|
|
Used for:
|
|
- provider-agnostic provisioning strategy
|
|
|
|
## 11. Note On Source Priority
|
|
|
|
For technical decisions, this proposal prioritizes primary official documentation and release notes over secondary summaries.
|