@synap-core/cli 1.8.0 → 1.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (332) hide show
  1. package/dist/commands/agent-chat.d.ts +47 -0
  2. package/dist/commands/agent-chat.js +250 -0
  3. package/dist/commands/agent-chat.js.map +1 -0
  4. package/dist/commands/agent-run.js +3 -4
  5. package/dist/commands/agent-run.js.map +1 -1
  6. package/dist/commands/agents.js +85 -46
  7. package/dist/commands/agents.js.map +1 -1
  8. package/dist/commands/automation.js +2 -1
  9. package/dist/commands/automation.js.map +1 -1
  10. package/dist/commands/bridge-setup.d.ts +66 -0
  11. package/dist/commands/bridge-setup.js +1112 -0
  12. package/dist/commands/bridge-setup.js.map +1 -0
  13. package/dist/commands/cap-connections.d.ts +28 -0
  14. package/dist/commands/cap-connections.js +224 -0
  15. package/dist/commands/cap-connections.js.map +1 -0
  16. package/dist/commands/capability.d.ts +89 -0
  17. package/dist/commands/capability.js +1523 -0
  18. package/dist/commands/capability.js.map +1 -0
  19. package/dist/commands/centrality.d.ts +20 -0
  20. package/dist/commands/centrality.js +94 -0
  21. package/dist/commands/centrality.js.map +1 -0
  22. package/dist/commands/connect.d.ts +2 -0
  23. package/dist/commands/connect.js +16 -35
  24. package/dist/commands/connect.js.map +1 -1
  25. package/dist/commands/context.js +4 -6
  26. package/dist/commands/context.js.map +1 -1
  27. package/dist/commands/data-extra.d.ts +1 -0
  28. package/dist/commands/data-extra.js +34 -10
  29. package/dist/commands/data-extra.js.map +1 -1
  30. package/dist/commands/data.d.ts +4 -4
  31. package/dist/commands/data.js +241 -184
  32. package/dist/commands/data.js.map +1 -1
  33. package/dist/commands/diagnose.d.ts +20 -0
  34. package/dist/commands/diagnose.js +143 -0
  35. package/dist/commands/diagnose.js.map +1 -0
  36. package/dist/commands/digest.d.ts +17 -0
  37. package/dist/commands/digest.js +121 -0
  38. package/dist/commands/digest.js.map +1 -0
  39. package/dist/commands/discover.d.ts +2 -0
  40. package/dist/commands/discover.js +25 -8
  41. package/dist/commands/discover.js.map +1 -1
  42. package/dist/commands/events.js +2 -1
  43. package/dist/commands/events.js.map +1 -1
  44. package/dist/commands/explain.d.ts +1 -1
  45. package/dist/commands/explain.js +18 -15
  46. package/dist/commands/explain.js.map +1 -1
  47. package/dist/commands/facet.d.ts +29 -0
  48. package/dist/commands/facet.js +113 -0
  49. package/dist/commands/facet.js.map +1 -0
  50. package/dist/commands/graph.js +2 -1
  51. package/dist/commands/graph.js.map +1 -1
  52. package/dist/commands/import.d.ts +38 -0
  53. package/dist/commands/import.js +440 -0
  54. package/dist/commands/import.js.map +1 -0
  55. package/dist/commands/init.js +35 -16
  56. package/dist/commands/init.js.map +1 -1
  57. package/dist/commands/keys.js +3 -4
  58. package/dist/commands/keys.js.map +1 -1
  59. package/dist/commands/knowledge.d.ts +2 -0
  60. package/dist/commands/knowledge.js +61 -9
  61. package/dist/commands/knowledge.js.map +1 -1
  62. package/dist/commands/launch.d.ts +50 -0
  63. package/dist/commands/launch.js +790 -0
  64. package/dist/commands/launch.js.map +1 -0
  65. package/dist/commands/lens.d.ts +45 -0
  66. package/dist/commands/lens.js +386 -0
  67. package/dist/commands/lens.js.map +1 -0
  68. package/dist/commands/market.d.ts +209 -0
  69. package/dist/commands/market.js +1368 -0
  70. package/dist/commands/market.js.map +1 -0
  71. package/dist/commands/mcp.d.ts +42 -0
  72. package/dist/commands/mcp.js +184 -0
  73. package/dist/commands/mcp.js.map +1 -0
  74. package/dist/commands/observe.js +14 -11
  75. package/dist/commands/observe.js.map +1 -1
  76. package/dist/commands/open.d.ts +21 -4
  77. package/dist/commands/open.js +45 -4
  78. package/dist/commands/open.js.map +1 -1
  79. package/dist/commands/pod.d.ts +100 -0
  80. package/dist/commands/pod.js +359 -0
  81. package/dist/commands/pod.js.map +1 -0
  82. package/dist/commands/pods.d.ts +1 -0
  83. package/dist/commands/pods.js +77 -15
  84. package/dist/commands/pods.js.map +1 -1
  85. package/dist/commands/proposals-actions.js +40 -3
  86. package/dist/commands/proposals-actions.js.map +1 -1
  87. package/dist/commands/purge.d.ts +23 -0
  88. package/dist/commands/purge.js +148 -0
  89. package/dist/commands/purge.js.map +1 -0
  90. package/dist/commands/raycast.d.ts +15 -0
  91. package/dist/commands/raycast.js +153 -0
  92. package/dist/commands/raycast.js.map +1 -0
  93. package/dist/commands/sessions.js +45 -21
  94. package/dist/commands/sessions.js.map +1 -1
  95. package/dist/commands/skill-manage.d.ts +21 -0
  96. package/dist/commands/skill-manage.js +195 -0
  97. package/dist/commands/skill-manage.js.map +1 -0
  98. package/dist/commands/skills-commands.js +2 -1
  99. package/dist/commands/skills-commands.js.map +1 -1
  100. package/dist/commands/skills.js +4 -3
  101. package/dist/commands/skills.js.map +1 -1
  102. package/dist/commands/status.d.ts +3 -1
  103. package/dist/commands/status.js +166 -14
  104. package/dist/commands/status.js.map +1 -1
  105. package/dist/commands/statusline.d.ts +24 -0
  106. package/dist/commands/statusline.js +450 -0
  107. package/dist/commands/statusline.js.map +1 -0
  108. package/dist/commands/subscribe.js +2 -2
  109. package/dist/commands/subscribe.js.map +1 -1
  110. package/dist/commands/tools.d.ts +30 -0
  111. package/dist/commands/tools.js +315 -0
  112. package/dist/commands/tools.js.map +1 -0
  113. package/dist/commands/versions.d.ts +27 -0
  114. package/dist/commands/versions.js +277 -0
  115. package/dist/commands/versions.js.map +1 -0
  116. package/dist/commands/view.js +3 -2
  117. package/dist/commands/view.js.map +1 -1
  118. package/dist/commands/whoami.d.ts +21 -0
  119. package/dist/commands/whoami.js +129 -0
  120. package/dist/commands/whoami.js.map +1 -0
  121. package/dist/index.js +776 -60
  122. package/dist/index.js.map +1 -1
  123. package/dist/lib/approval-poll.d.ts +42 -0
  124. package/dist/lib/approval-poll.js +52 -0
  125. package/dist/lib/approval-poll.js.map +1 -0
  126. package/dist/lib/auth.d.ts +29 -6
  127. package/dist/lib/auth.js +105 -94
  128. package/dist/lib/auth.js.map +1 -1
  129. package/dist/lib/bundle-version.d.ts +11 -0
  130. package/dist/lib/bundle-version.js +33 -0
  131. package/dist/lib/bundle-version.js.map +1 -0
  132. package/dist/lib/capture-lane.d.ts +30 -12
  133. package/dist/lib/capture-lane.js +71 -14
  134. package/dist/lib/capture-lane.js.map +1 -1
  135. package/dist/lib/cp-packages.d.ts +121 -0
  136. package/dist/lib/cp-packages.js +218 -0
  137. package/dist/lib/cp-packages.js.map +1 -0
  138. package/dist/lib/describe-lens.d.ts +46 -0
  139. package/dist/lib/describe-lens.js +33 -0
  140. package/dist/lib/describe-lens.js.map +1 -0
  141. package/dist/lib/hub-client.d.ts +78 -1
  142. package/dist/lib/hub-client.js +474 -22
  143. package/dist/lib/hub-client.js.map +1 -1
  144. package/dist/lib/installed.d.ts +51 -0
  145. package/dist/lib/installed.js +70 -0
  146. package/dist/lib/installed.js.map +1 -0
  147. package/dist/lib/next-steps.d.ts +61 -0
  148. package/dist/lib/next-steps.js +146 -0
  149. package/dist/lib/next-steps.js.map +1 -0
  150. package/dist/lib/pod.d.ts +91 -19
  151. package/dist/lib/pod.js +222 -56
  152. package/dist/lib/pod.js.map +1 -1
  153. package/dist/lib/project-ref.d.ts +95 -0
  154. package/dist/lib/project-ref.js +144 -0
  155. package/dist/lib/project-ref.js.map +1 -0
  156. package/dist/lib/project.d.ts +35 -0
  157. package/dist/lib/project.js +39 -0
  158. package/dist/lib/project.js.map +1 -0
  159. package/dist/lib/session-lens.d.ts +33 -0
  160. package/dist/lib/session-lens.js +76 -0
  161. package/dist/lib/session-lens.js.map +1 -0
  162. package/dist/lib/skill-import.d.ts +40 -0
  163. package/dist/lib/skill-import.js +203 -0
  164. package/dist/lib/skill-import.js.map +1 -0
  165. package/dist/lib/skills-installer.d.ts +17 -6
  166. package/dist/lib/skills-installer.js +133 -19
  167. package/dist/lib/skills-installer.js.map +1 -1
  168. package/dist/lib/suite.d.ts +28 -0
  169. package/dist/lib/suite.js +29 -0
  170. package/dist/lib/suite.js.map +1 -0
  171. package/dist/lib/superwhisper-import.d.ts +40 -0
  172. package/dist/lib/superwhisper-import.js +389 -0
  173. package/dist/lib/superwhisper-import.js.map +1 -0
  174. package/dist/lib/targets.d.ts +49 -1
  175. package/dist/lib/targets.js +420 -288
  176. package/dist/lib/targets.js.map +1 -1
  177. package/dist/lib/unwrapList.d.ts +1 -0
  178. package/dist/lib/unwrapList.js +20 -0
  179. package/dist/lib/unwrapList.js.map +1 -0
  180. package/dist/utils/logger.d.ts +2 -0
  181. package/dist/utils/logger.js +10 -2
  182. package/dist/utils/logger.js.map +1 -1
  183. package/package.json +9 -4
  184. package/skills/agent-os/SKILL.md +212 -0
  185. package/skills/manifest.json +5 -0
  186. package/skills/onboard/SKILL.md +186 -0
  187. package/skills/synap/SKILL.md +1182 -37
  188. package/skills/synap/_order.txt +37 -0
  189. package/skills/synap/_skill.yaml +24 -0
  190. package/skills/synap/authentication.md +10 -0
  191. package/skills/synap/automations.md +264 -0
  192. package/skills/synap/capabilities.md +107 -0
  193. package/skills/synap/capture.md +10 -0
  194. package/skills/synap/cli-operations.md +107 -0
  195. package/skills/synap/common-mistakes.md +12 -0
  196. package/skills/synap/creative-loop.md +43 -0
  197. package/skills/synap/crm.md +117 -0
  198. package/skills/synap/diagnostics.md +35 -0
  199. package/skills/synap/digesting-a-channel.md +38 -0
  200. package/skills/synap/document-embeds.md +123 -0
  201. package/skills/synap/escalation-ladder.md +71 -0
  202. package/skills/synap/focus-sessions.md +47 -0
  203. package/skills/synap/governance-rules.md +64 -0
  204. package/skills/synap/governance.md +6 -6
  205. package/skills/synap/graph-gardening.md +21 -0
  206. package/skills/synap/inline-patterns.md +38 -0
  207. package/skills/synap/lenses.md +38 -0
  208. package/skills/synap/linking-principle.md +39 -0
  209. package/skills/synap/linking.md +1 -0
  210. package/skills/synap/mental-model.md +45 -0
  211. package/skills/synap/more.md +7 -0
  212. package/skills/synap/multi-entity-capture.md +10 -0
  213. package/skills/synap/next-action.md +37 -0
  214. package/skills/synap/north-star.md +17 -0
  215. package/skills/synap/operating-mode-rules.md +45 -0
  216. package/skills/synap/operating-mode.md +9 -0
  217. package/skills/synap/quick-reference.md +67 -0
  218. package/skills/synap/reading.md +43 -0
  219. package/skills/synap/recap.md +21 -0
  220. package/skills/synap/reflexes.md +46 -0
  221. package/skills/synap/response-style.md +21 -0
  222. package/skills/synap/scope.md +13 -0
  223. package/skills/synap/showing.md +17 -0
  224. package/skills/synap/user-model.md +25 -0
  225. package/skills/synap/viewframe-cells.md +290 -0
  226. package/skills/synap/work-flow.md +113 -0
  227. package/skills/synap/worked-examples.md +53 -0
  228. package/skills/synap/workspace-design.md +45 -0
  229. package/skills/synap/workspace-edges.md +49 -0
  230. package/skills/synap/writes.md +156 -0
  231. package/skills/synap-schema/SKILL.md +97 -6
  232. package/skills/synap-schema/_order.txt +13 -0
  233. package/skills/synap-schema/_skill.yaml +22 -0
  234. package/skills/synap-schema/before-you-touch.md +14 -0
  235. package/skills/synap-schema/common-mistakes.md +9 -0
  236. package/skills/synap-schema/creating-profiles.md +17 -0
  237. package/skills/synap-schema/discover-profiles.md +24 -0
  238. package/skills/synap-schema/entity-scope.md +8 -0
  239. package/skills/synap-schema/extend-vs-create.md +31 -0
  240. package/skills/synap-schema/more.md +6 -0
  241. package/skills/synap-schema/overlay-properties.md +22 -0
  242. package/skills/synap-schema/profiles.md +3 -0
  243. package/skills/synap-schema/property-defs.md +29 -0
  244. package/skills/synap-schema/read-before-write.md +50 -0
  245. package/skills/synap-schema/relations.md +18 -0
  246. package/skills/synap-schema/worked-example.md +30 -0
  247. package/skills/synap-ui/SKILL.md +26 -2
  248. package/skills/synap-ui/_order.txt +13 -0
  249. package/skills/synap-ui/_skill.yaml +23 -0
  250. package/skills/synap-ui/ai-companion.md +27 -0
  251. package/skills/synap-ui/arranging-bento.md +8 -0
  252. package/skills/synap-ui/before-you-build.md +20 -0
  253. package/skills/synap-ui/bento-layouts.md +35 -0
  254. package/skills/synap-ui/common-mistakes.md +10 -0
  255. package/skills/synap-ui/creating-views.md +26 -0
  256. package/skills/synap-ui/four-builds.md +24 -0
  257. package/skills/synap-ui/more.md +7 -0
  258. package/skills/synap-ui/proposing-vs-extending.md +11 -0
  259. package/skills/synap-ui/view-list.md +24 -0
  260. package/skills/synap-ui/views.md +3 -0
  261. package/skills/synap-ui/worked-example.md +18 -0
  262. package/skills/synap-ui/workspaces.md +47 -0
  263. package/templates/automations/bookmark-enrichment.automation.json +44 -0
  264. package/templates/automations/mail-feed.automation.json +86 -0
  265. package/templates/automations/url-bookmark-capture.automation.json +70 -0
  266. package/templates/skills/README.md +21 -0
  267. package/templates/skills/authoring-automations/SKILL.md +95 -0
  268. package/templates/skills/authoring-automations/reference/node-matrix.md +49 -0
  269. package/templates/skills/authoring-capabilities/SKILL.md +93 -0
  270. package/templates/skills/authoring-capabilities/reference/template-anatomy.md +70 -0
  271. package/templates/skills/authoring-playbooks/SKILL.md +102 -0
  272. package/templates/skills/authoring-playbooks/reference/stages-contract.md +35 -0
  273. package/templates/skills/authoring-playbooks/reference/worked-example.md +64 -0
  274. package/templates/skills/bookmark-enrichment/SKILL.md +40 -0
  275. package/templates/skills/coordinating-agents/SKILL.md +32 -0
  276. package/templates/skills/coordinating-branches/SKILL.md +27 -0
  277. package/templates/skills/mapping-the-server/SKILL.md +54 -0
  278. package/templates/skills/reading-client-progress/SKILL.md +65 -0
  279. package/templates/skills/routing-to-channels/SKILL.md +54 -0
  280. package/templates/skills/stellar-scf-grants-advisor/ASSOCIATE-CHEATSHEET.md +133 -0
  281. package/templates/skills/stellar-scf-grants-advisor/ASSOCIATE-ONBOARDING-GUIDE.md +761 -0
  282. package/templates/skills/stellar-scf-grants-advisor/CLIENT-FAQ.md +181 -0
  283. package/templates/skills/stellar-scf-grants-advisor/PARTNER-HANDOVER.md +130 -0
  284. package/templates/skills/stellar-scf-grants-advisor/SKILL.md +102 -0
  285. package/templates/skills/stellar-scf-grants-advisor/examples/README.md +43 -0
  286. package/templates/skills/stellar-scf-grants-advisor/examples/chat-summary-templates.md +158 -0
  287. package/templates/skills/stellar-scf-grants-advisor/examples/corpus-comparable-rows.md +136 -0
  288. package/templates/skills/stellar-scf-grants-advisor/examples/q10-team-rewrites.md +109 -0
  289. package/templates/skills/stellar-scf-grants-advisor/examples/q2-description-rewrites.md +88 -0
  290. package/templates/skills/stellar-scf-grants-advisor/examples/q6-integration-rewrites.md +107 -0
  291. package/templates/skills/stellar-scf-grants-advisor/examples/tranche-structures.md +176 -0
  292. package/templates/skills/stellar-scf-grants-advisor/reference/01-methodology.md +96 -0
  293. package/templates/skills/stellar-scf-grants-advisor/reference/02-scoring-framework.md +199 -0
  294. package/templates/skills/stellar-scf-grants-advisor/reference/03-rejection-patterns.md +241 -0
  295. package/templates/skills/stellar-scf-grants-advisor/reference/04-winner-patterns.md +120 -0
  296. package/templates/skills/stellar-scf-grants-advisor/reference/05-comeback-patterns.md +92 -0
  297. package/templates/skills/stellar-scf-grants-advisor/reference/06-budget-benchmarks.md +125 -0
  298. package/templates/skills/stellar-scf-grants-advisor/reference/07-integration-list.md +147 -0
  299. package/templates/skills/stellar-scf-grants-advisor/reference/08-abstract-fields.md +258 -0
  300. package/templates/skills/stellar-scf-grants-advisor/reference/09-build-fields.md +259 -0
  301. package/templates/skills/stellar-scf-grants-advisor/reference/10-corpus-winners.md +135 -0
  302. package/templates/skills/stellar-scf-grants-advisor/reference/11-corpus-rejects.md +267 -0
  303. package/templates/skills/stellar-scf-grants-advisor/reference/12-client-communication.md +131 -0
  304. package/templates/skills/stellar-scf-grants-advisor/reference/13-excel-output-spec.md +199 -0
  305. package/templates/skills/stellar-scf-grants-advisor/reference/14-worked-examples.md +160 -0
  306. package/templates/skills/stellar-scf-grants-advisor/templates/abstract-review-builder.py +253 -0
  307. package/templates/skills/stellar-scf-grants-advisor/templates/build-review-builder.py +213 -0
  308. package/dist/commands/connectors.d.ts +0 -31
  309. package/dist/commands/connectors.js +0 -276
  310. package/dist/commands/connectors.js.map +0 -1
  311. package/dist/commands/finish.d.ts +0 -25
  312. package/dist/commands/finish.js +0 -274
  313. package/dist/commands/finish.js.map +0 -1
  314. package/dist/commands/openclaw.d.ts +0 -40
  315. package/dist/commands/openclaw.js +0 -1148
  316. package/dist/commands/openclaw.js.map +0 -1
  317. package/dist/commands/security-audit.d.ts +0 -12
  318. package/dist/commands/security-audit.js +0 -100
  319. package/dist/commands/security-audit.js.map +0 -1
  320. package/dist/lib/hardening.d.ts +0 -18
  321. package/dist/lib/hardening.js +0 -214
  322. package/dist/lib/hardening.js.map +0 -1
  323. package/node_modules/@synap/hub-rest-client/dist/index.cjs +0 -881
  324. package/node_modules/@synap/hub-rest-client/dist/index.d.cts +0 -907
  325. package/node_modules/@synap/hub-rest-client/dist/index.d.ts +0 -907
  326. package/node_modules/@synap/hub-rest-client/dist/index.js +0 -851
  327. package/node_modules/@synap/hub-rest-client/package.json +0 -45
  328. package/node_modules/@synap/hub-rest-client/src/client.ts +0 -1143
  329. package/node_modules/@synap/hub-rest-client/src/errors.ts +0 -30
  330. package/node_modules/@synap/hub-rest-client/src/index.ts +0 -111
  331. package/node_modules/@synap/hub-rest-client/src/setup.ts +0 -77
  332. package/node_modules/@synap/hub-rest-client/src/types.ts +0 -639
@@ -0,0 +1,120 @@
1
+ # Common winning patterns in past SCF rounds
2
+
3
+ Mirror image of `03-rejection-patterns.md`. These are the attributes that show up in the 79+ awarded SCF dossiers we have catalogued across rounds #40, #41, #42 and prior.
4
+
5
+ A dossier that hits all eight patterns has a near-deterministic shot at being funded. Most winners hit five or six.
6
+
7
+ ## Pattern A: a fully doxxed founding team with verifiable past shipping
8
+
9
+ **What it looks like:** each named founder has a LinkedIn URL, the CTO has a GitHub URL with public code, and at least one founder has shipped a prior product (Web2 or Web3) that the panel can verify.
10
+
11
+ **Why this wins:** answers the "can you ship?" question definitively.
12
+
13
+ **Past winners with this pattern:**
14
+ - The Signal ($121K in SCF #42), Samir Touinssi (Arch Consulting, content creator 10+ years) + Leo Leung (Imperial Physics, Orichal Partners quant researcher) both fully doxxed.
15
+ - Bando ($75K in SCF #42), Mexican team fully doxxed with named pilot customer.
16
+ - TheXBank ($89.5K in SCF #40), Africa banking team doxxed with country pilot.
17
+ - DeFindex (prior), Palta Labs team verifiable, public Discord.
18
+
19
+ ## Pattern B: a Soroban contract that is the project's net-new primitive
20
+
21
+ **What it looks like:** the dossier names a specific Soroban contract (DealEscrow.rs, YieldVault.rs, GreenBondToken.rs) that the team will develop and open-source under MIT. The contract is the core innovation; everything else (wallets, anchors, indexers) is integration.
22
+
23
+ **Why this wins:** anchors the dossier as an Integration Track or Open Track that builds reusable ecosystem infrastructure rather than a closed product.
24
+
25
+ **Past winners with this pattern:**
26
+ - The Signal, DealEscrow.rs with Atomic Splits payout logic.
27
+ - DeFindex, yield allocator routing contract.
28
+ - Bando, RWA tokenization contract.
29
+
30
+ ## Pattern C: clear use of multiple SCF Integration List items
31
+
32
+ **What it looks like:** the Q6 Integration Description names at least 3 components from the official Stellar Integration List (Stellar Wallets Kit, Passkey Kit, Anchor Platform, Privy, DeFindex, Blend v2, Aquarius, Soroswap, Allbridge, Near Intents, etc.) with a clear role for each.
33
+
34
+ **Why this wins:** demonstrates the dossier understands the ecosystem and is wiring into existing primitives rather than building from scratch. This is exactly what Integration Track was designed to fund.
35
+
36
+ **Past winners with this pattern:**
37
+ - The Signal, used wallet connectors and routing primitives.
38
+ - Bando, Anchor Platform plus wallet stack.
39
+ - Future winners following For Yield (target $144K), 7 Integration List items named.
40
+
41
+ ## Pattern D: a B2B distribution story with named customers or partners
42
+
43
+ **What it looks like:** the Q4 Traction or Q9 Traction Evidence names specific brands, pilot customers, signed Letters of Intent, or regulated partners. Not "in discussions with several X", but "signed LOI with [Named Entity]".
44
+
45
+ **Why this wins:** removes the "who will use this?" question from the panel's worry list.
46
+
47
+ **Past winners with this pattern:**
48
+ - The Signal, pre-launch but named the Web3 service provider categories and the bridge value proposition.
49
+ - Bando, named brokerage partner in Mexico.
50
+ - TheXBank, country pilot named with specifics.
51
+
52
+ ## Pattern E: budget sub-max and anchored on a precedent
53
+
54
+ **What it looks like:** the requested budget is between $75K and $135K (sub-max), structured as 3 equivalent tranches, and the dossier explicitly references a past winner with comparable scope.
55
+
56
+ **Why this wins:** avoids the heightened scrutiny that applies to $145K-$150K asks, and signals the team has done the work of calibrating their request.
57
+
58
+ **Past winners with this pattern:**
59
+ - Bando ($75K), kept narrow scope.
60
+ - TheXBank ($89.5K), kept narrow scope.
61
+ - The Signal ($121K), sub-max with full scope.
62
+
63
+ ## Pattern F: explicit alignment with SDF roadmap priorities
64
+
65
+ **What it looks like:** the dossier mentions one or more current SDF strategic priorities (x402 micropayments, Protocol 25 X-Ray ZK primitives, EURC adoption, MiCA EU institutional access, agentic payments) and explains how the project leverages or extends them.
66
+
67
+ **Why this wins:** signals the team is paying attention to where the foundation wants ecosystem growth.
68
+
69
+ **Past winners with this pattern:**
70
+ - DeFindex aligns with DeFi infrastructure growth.
71
+ - Bando aligns with RWA growth.
72
+
73
+ ## Pattern G: open-source commitment on all Soroban contracts
74
+
75
+ **What it looks like:** Q6 Integration explicitly commits to publishing the Soroban contracts under MIT (or Apache 2.0) on a public GitHub repository.
76
+
77
+ **Why this wins:** SCF is a public-good fund. Open-source primitives multiply the grant's impact across the ecosystem.
78
+
79
+ **Past winners with this pattern:**
80
+ - DeFindex, open-source.
81
+ - Aquarius, open-source.
82
+ - Blend, open-source.
83
+
84
+ ## Pattern H: a regulated category with a fully-named regulatory plan
85
+
86
+ **What it looks like:** for regulated categories (payments, lending, securities, RWA), the dossier names the specific framework (Art L.411-2 CMF, MiFID II, MiCA, PSCA AMF, BIN sponsor), the named licensing partner, and the KYC vendor.
87
+
88
+ **Why this wins:** turns a high-risk category into a credible execution plan.
89
+
90
+ **Past winners with this pattern:**
91
+ - The Signal, clear positioning as Integration Track wrapping existing primitives, no regulatory blocker.
92
+ - Bando, RWA real estate Mexico with brokerage partner named.
93
+ - Future winners following For Yield and Rebond, full regulatory framework cited.
94
+
95
+ ## Combination winning profile
96
+
97
+ The dossiers that win most often combine patterns A + B + C + D + E. Adding F, G, H raises the probability further. Missing any of A, D, or H (when in a regulated category) is usually fatal regardless of other strengths.
98
+
99
+ ## A specific reference case: The Signal ($121K SCF #42 winner)
100
+
101
+ Samir Touinssi and Leo Leung submitted The Signal as a Soroban-based escrow for Web3 service providers. The dossier hit:
102
+
103
+ - Pattern A: both founders fully doxxed with LinkedIn.
104
+ - Pattern B: DealEscrow.rs as the net-new Soroban primitive.
105
+ - Pattern C: named Stellar SDK, Freighter, Albedo wallets.
106
+ - Pattern D: named Web3 service provider categories with specific commission bounty mechanics.
107
+ - Pattern E: $121K (sub-max), three equivalent tranches.
108
+ - Pattern G: open-source commitment on the escrow contract.
109
+
110
+ It missed patterns F (no explicit x402 or Protocol 25 alignment) and H (no regulatory framework needed for B2B escrow). Five-of-eight pattern coverage was enough to win.
111
+
112
+ Use this as the working template for budget anchoring on the $100K-$130K range.
113
+
114
+ ## How to surface these patterns in a client review
115
+
116
+ When you review a dossier, identify the winning patterns it already has. Tell the client. This is part of the value: clients often do not know their own strengths. Examples of plain-English framing for the client:
117
+
118
+ - *"Your team section already hits one of the patterns we see most often in past SCF winners: every co-founder has a verifiable LinkedIn URL and the CTO has a public GitHub. This is the single most reliable predictor of acceptance in our database."*
119
+
120
+ - *"Your traction section is in the top 10 percent of dossiers we have reviewed: signed LOIs with four named clients and two regulated distribution partners. This profile won The Signal $121K in SCF #42 and is what we're anchoring your budget recommendation on."*
@@ -0,0 +1,92 @@
1
+ # Comeback patterns: from rejection to award
2
+
3
+ Some teams that lost a round came back and won a later one. We have catalogued thirteen such cases. The pattern of changes is consistent. Use this document when a client is reapplying after a previous rejection.
4
+
5
+ ## The thirteen comeback moves
6
+
7
+ Each move is a specific change between the rejected dossier and the winning dossier. Most successful comebacks apply two to four of these moves at once.
8
+
9
+ ### Move 1: reframe the deliverable from feature-level to protocol-level
10
+
11
+ The rejected dossier described a feature ("a better swap UI"); the winner reframed it as a protocol ("a Soroban routing primitive other teams can fork").
12
+
13
+ **Why it works:** SCF wants reusable infrastructure, not closed features.
14
+
15
+ ### Move 2: replace anonymous handles with full names plus LinkedIn
16
+
17
+ Pattern 1 in `03-rejection-patterns.md`. The single highest-impact fix when present.
18
+
19
+ ### Move 3: right-size the budget down from $150K to $80K-$130K with sharper scope
20
+
21
+ Pattern 2. Reducing the ask and tightening the deliverable often turns a rejected dossier into a winner.
22
+
23
+ ### Move 4: add a named pilot customer or integration partner before resubmitting
24
+
25
+ Move from "in discussions with X" to "signed LOI with Y, named in the dossier". Bando $75K winner did this. AveForge can do this with Stellar protocol contacts before Build phase.
26
+
27
+ ### Move 5: pivot from a saturated category to an adjacent under-funded niche
28
+
29
+ If your category lost the prior round to another funded team, find a sharper sub-niche. Lend.xyz lost to Bando in RWA real estate; a reapplication should pick a different vertical or sharper geography.
30
+
31
+ ### Move 6: switch Track (Open vs Integration) based on what the proposal actually is
32
+
33
+ A pure Soroban contract with no ecosystem dependencies should be Open Track. A wrap of existing primitives plus a wallet stack should be Integration Track. Picking the wrong Track gets the wrong evaluation criteria.
34
+
35
+ ### Move 7: ship a Soroban testnet contract before submitting
36
+
37
+ A live testnet contract address in Q5 Code URL transforms a "we will deploy" claim into a "we are deploying" demonstration. Five to seven days of work to ship a minimal contract.
38
+
39
+ ### Move 8: replace "we will validate post-grant" with documented pre-grant traction
40
+
41
+ Move from "we plan to test this" to "we tested this with 30 users last quarter and the result was X". Bando did this with their Mexican pilot.
42
+
43
+ ### Move 9: explicitly acknowledge the prior gap in the abstract
44
+
45
+ Panel respects self-awareness. One sentence in Q9 Build phase: "We addressed the prior panel feedback by [specific change]." This is signal 14 in the scoring framework.
46
+
47
+ ### Move 10: replace vague TAM with country + city + persona + first 100 users
48
+
49
+ Pattern 9 fix. Replace "pan-Africa" with "Lagos, Nigeria via [Named Partner], targeting [Specific Persona] for first 100 users".
50
+
51
+ ### Move 11: drop overlap claims and reposition as a complement to an already-funded peer
52
+
53
+ Instead of competing with a funded project, position as the layer above or below it. For Yield does this by positioning as the regulated EU access layer on top of DeFindex, Blend, Aquarius (all prior winners).
54
+
55
+ ### Move 12: add a regulatory partner name plus jurisdiction to any regulated-category submission
56
+
57
+ Pattern 8 fix. Name the framework, name the partner, show the filing.
58
+
59
+ ### Move 13: publish open-source primitives so the project reads as ecosystem infrastructure, not closed SaaS
60
+
61
+ Move from "SaaS that uses Stellar" to "Soroban primitive that anyone can fork, plus a hosted instance we run".
62
+
63
+ ## Worked example: a hypothetical comeback
64
+
65
+ A team submitted an Abstract last round with this profile:
66
+ - Solo dev, only known by handle "Mintro"
67
+ - $150K ask for "an event ticketing platform"
68
+ - Vague TAM ("global creator economy")
69
+ - No Soroban contract named
70
+ - No regulatory framework cited
71
+ - No LOIs
72
+
73
+ Rejected (Panel Review Failed). The team comes back six months later wanting to resubmit.
74
+
75
+ Apply moves 2, 3, 4, 7, 10, 13:
76
+
77
+ - **Move 2:** Mintro adds full name and LinkedIn, finds a doxxed co-founder with ticketing industry background.
78
+ - **Move 3:** budget drops to $121K (matched to The Signal winner), three equivalent tranches.
79
+ - **Move 4:** secured one signed LOI with a named B2B venue (300-seat theatre) for the first mainnet deal.
80
+ - **Move 7:** shipped a TicketRegistry.rs contract to testnet, address in Q5 Code URL.
81
+ - **Move 10:** replaced "global creator economy" with "Paris-region independent venues, first 5 partners via [Named Distribution Partner], targeting 100 events in Year 1".
82
+ - **Move 13:** committed to MIT open-source on TicketRegistry.rs, GitHub URL provided.
83
+
84
+ Probability went from 15 percent to 55 percent. Whether this team wins depends on additional moves (regulatory framework if they handle ticket secondary market in France, named vault partner, etc.) but the basic moves alone shifted the dossier from "almost certain rejection" to "competitive".
85
+
86
+ ## The honest framing for the client
87
+
88
+ When you advise a client who is reapplying, be direct:
89
+
90
+ > *"Your previous submission triggered three of the recurring rejection patterns we've documented in our database. We can address all three before the next round. Specifically: we'll add a co-founder with a verifiable LinkedIn to fix the team accountability gap (this alone shifts your odds by roughly 15 to 25 percent), reduce the budget from $150K to $121K to align with The Signal winner ($121K in SCF #42), and replace the vague distribution plan with a named pilot in [specific city]. Three changes, six weeks of work, double-digit probability lift."*
91
+
92
+ That tone (specific, anchored on data, honest about effort) is what wins comeback engagements.
@@ -0,0 +1,125 @@
1
+ # Budget benchmarks: how to recommend the right ask
2
+
3
+ Every review ends with a budget recommendation. This document gives you the anchors.
4
+
5
+ ## The corpus budget table
6
+
7
+ Past winners and target budgets, ordered by size, with the profile that justified each amount.
8
+
9
+ | Project | SCF round | Budget | Team size | Contracts | Key justifier |
10
+ |---|---|---|---|---|---|
11
+ | Bando | #42 | $75,000 | 3-4 doxxed | 1 RWA tokenizer | Mexican real-estate pilot named, brokerage partner named |
12
+ | TheXBank | #40 | $89,500 | doxxed | banking infra | Africa country pilot named, doxxed team |
13
+ | The Signal | #42 | $121,000 | 2 doxxed | 1 escrow (DealEscrow.rs) + Atomic Splits | B2B marketplace with named verticals, ecosystem integrations |
14
+ | Rebond | #44 (target) | $132,000 | 2 doxxed | 3 (GreenBondToken, KYCWhitelist, CouponDistributor) | 4 LOIs signed, 2 distribution partners, Art L.411-2 framework |
15
+ | For Yield | #44 (target) | $144,000 | 11 doxxed | 3 (YieldVault, PerfFeeModule, EURC SAC wrapper) | PSCA AMF filed, €7-8M AUM, 50 HNW clients onboarded |
16
+
17
+ Maximum permitted ask is $150K. Anything between $145K and $150K triggers heightened scrutiny. Most winners sit between $75K and $135K.
18
+
19
+ ## How to pick the right anchor for a new dossier
20
+
21
+ Match the new dossier to its closest profile in the table above, then position it one tier up or down depending on three factors:
22
+
23
+ 1. **Team size.** Each additional doxxed team member with verifiable credentials supports roughly +$3K to +$5K of ask.
24
+
25
+ 2. **Contract scope.** Each additional named Soroban contract supports roughly +$8K to +$12K of ask (one contract: $80K to $90K floor; three contracts: $130K to $145K range).
26
+
27
+ 3. **Traction and partner depth.** Each named pilot customer (with signed LOI) or named regulated distribution partner supports roughly +$5K to +$10K.
28
+
29
+ ## Worked anchors for current categories
30
+
31
+ ### B2B marketplace or escrow with Soroban Atomic Splits
32
+
33
+ Anchor: The Signal $121K winner.
34
+
35
+ Recommended range: $115,000 to $135,000.
36
+ - Sub-$120K if smaller team or single contract.
37
+ - $130K+ if multiple contracts plus named B2B partners.
38
+
39
+ ### Regulated DeFi yield or vault
40
+
41
+ Anchor: For Yield $144K target (PSCA AMF, 11-team, €7-8M AUM).
42
+
43
+ Recommended range: $115,000 to $144,000.
44
+ - $115K-$125K if no regulatory filing in progress.
45
+ - $130K-$144K if AMF or comparable regulator filing in progress and named LOIs.
46
+
47
+ ### RWA tokenization (real estate, gold, bonds)
48
+
49
+ Anchor: Bando $75K winner for narrow pilot; Rebond $132K target for broader scope.
50
+
51
+ Recommended range: $75,000 to $132,000.
52
+ - $75K-$95K if single pilot customer or narrow geography.
53
+ - $100K-$132K if 3+ pilots, distribution partners, regulatory framework named.
54
+
55
+ ### Gaming or consumer earn-adjacent
56
+
57
+ Anchor: zero pure-play game has won in our corpus. Closest comparable is AveForge / Solar Braves target $121K-$132K.
58
+
59
+ Recommended range: $100,000 to $132,000.
60
+ - Strongly recommend sub-$135K given the high rejection rate for the category.
61
+ - The dossier must avoid the play-to-earn rejection pattern (see `03-rejection-patterns.md` Pattern 10).
62
+
63
+ ### DeFi infrastructure (yield, AMM, lending)
64
+
65
+ Anchor: DeFindex, Aquarius, Blend (all prior winners; budgets not always public).
66
+
67
+ Recommended range: $90,000 to $130,000.
68
+ - Soroban primitive plus ecosystem integrations.
69
+ - Open-source mandatory.
70
+
71
+ ### Compliance and tooling
72
+
73
+ Anchor: Latch + KMP (RFP winners SCF #41).
74
+
75
+ Recommended range: $70,000 to $110,000.
76
+ - Often narrow scope, more easily anchored on RFP-track precedent.
77
+
78
+ ## The sub-max rule
79
+
80
+ Almost no dossier in our corpus has won at $145K or $150K. Five recent rejected dossiers all maxed:
81
+ - StellarRead $150K, Easner $150K, Tessera Labs $150K, AION_FI $146.5K, $NRG Token $150K.
82
+
83
+ When in doubt, drop the ask by $5K-$10K below $145K. The signal cost of "max ask" is higher than the dollar value gained.
84
+
85
+ ## Tranche structure
86
+
87
+ SCF mandates three "equivalent" tranches. Equivalent means roughly equal, with reviewer flexibility on a few hundred dollars of variation.
88
+
89
+ Clean structures we recommend:
90
+ - $90,000 = 3 x $30,000.
91
+ - $99,000 = 3 x $33,000.
92
+ - $108,000 = 3 x $36,000.
93
+ - $120,000 = 3 x $40,000.
94
+ - $121,200 = 3 x $40,400.
95
+ - $132,000 = 3 x $44,000.
96
+ - $135,000 = 3 x $45,000.
97
+ - $144,000 = 3 x $48,000.
98
+
99
+ Avoid odd numbers like $123,500 that don't split cleanly; reviewers notice.
100
+
101
+ ## How to phrase a budget recommendation to the client
102
+
103
+ Always anchor on a named precedent. Example:
104
+
105
+ > *"Recommended budget: $121,200, structured as 3 tranches of $40,400. This matches The Signal exactly ($121K in SCF #42), which had a comparable profile: 2 cofounders fully doxxed, one Soroban contract with Atomic Splits, and B2B distribution. Staying at this exact anchor signals to reviewers that you have done the corpus-anchoring work. Going to $144K would push you toward the For Yield benchmark which requires a larger team and a regulatory filing, neither of which apply to your current profile. Going below $115K would underprice the scope: with three contracts plus a full game frontend plus a wallet onboarding stack, $115K is too low."*
106
+
107
+ That format (named anchor, scope justification, comparison to next-tier-up, floor justification) is the gold standard.
108
+
109
+ ## Special cases
110
+
111
+ ### A client who insists on $150K
112
+
113
+ Some clients want the maximum. Be honest:
114
+
115
+ > *"At $150K, your dossier enters the heightened scrutiny bucket. In our corpus, five dossiers were rejected at $145K-$150K specifically because they could not justify the maximum ask. The math: dropping to $132K loses you $18K but it shifts your rejection probability down by roughly 10 to 15 percentage points (worth roughly $14K to $20K of expected value). You probably want to take the lower ask."*
116
+
117
+ ### A client who insists on $50K (under-asking)
118
+
119
+ Some clients fear rejection so they under-ask. Also honest:
120
+
121
+ > *"At $50K, you may signal to the panel that you don't have a real plan. Our smallest funded comparable is Bando at $75K, and even that came with a fully named pilot customer. If your scope justifies $90K-$120K (named contracts plus ecosystem integrations plus a distribution channel), ask for it. Under-asking is sometimes worse than the right ask."*
122
+
123
+ ### A client at a "weird" amount like $127,300
124
+
125
+ Round to the nearest thousand and prefer clean tranche splits. The panel notices odd numbers.
@@ -0,0 +1,147 @@
1
+ # The official SCF Integration List
2
+
3
+ The Stellar Foundation maintains an official list of building blocks SCF reviewers expect Integration Track submissions to leverage. The list is at:
4
+
5
+ `https://stellar.gitbook.io/scf-handbook/scf-awards/build-award/integration-track/integration-list`
6
+
7
+ This document captures the items in the list at the time of this skill build, by category, with practical guidance for which to recommend per project profile.
8
+
9
+ ## How SCF uses the list
10
+
11
+ For Integration Track submissions, SCF expects the dossier to leverage at least one item from this list. The strongest dossiers leverage three to seven items. Reviewers explicitly check the Q6 Integration Description against this list.
12
+
13
+ For Open Track submissions, the dossier can develop a net-new primitive, but the surrounding workflow (wallets, anchors) should still use items from this list.
14
+
15
+ Items NOT on the list (Fireblocks, Wirex, Elliptic, Certora) can be mentioned as supporting infrastructure, but should not be presented as Integration Track items.
16
+
17
+ ## On / Off-ramping (Fiat Gateways)
18
+
19
+ These connect crypto and fiat. Recommend for any consumer-facing dossier where users need to onboard with local currency.
20
+
21
+ | Item | Integration time | Best for |
22
+ |---|---|---|
23
+ | Anchor Platform | 1+ month | Building your own anchor (issuer infrastructure for assets) |
24
+ | Bridge | 1-5 days | Multi-currency payments, Stripe-company partner |
25
+ | MoneyGram | 1+ month | Global cash-in/cash-out, emerging markets |
26
+ | Mercuryo | 1-2 weeks | Fiat-crypto on-ramp |
27
+ | BlindPay | 1-2 weeks | LATAM and global payments |
28
+ | Etherfuse | 1-2 weeks | Stablebonds backed by government bonds |
29
+ | alfredpay | unspecified | LATAM stablecoin to local banking rails |
30
+ | Abroad | 1-2 weeks | Digital wallets to local instant payment rails |
31
+
32
+ **Practical guidance:** for a French / EU consumer product, Anchor Platform plus optional Mercuryo or Bridge is the natural stack. For LATAM, Bridge plus alfredpay. For emerging markets cash usage, MoneyGram.
33
+
34
+ ## DeFi: Yield Aggregators
35
+
36
+ | Item | Integration time | Best for |
37
+ |---|---|---|
38
+ | DeFindex | 1-2 weeks | Yield infrastructure for Stellar wallets and DeFi apps |
39
+
40
+ **Practical guidance:** the only listed yield aggregator. Recommend for any project that needs yield routing across multiple Stellar DeFi venues.
41
+
42
+ ## DeFi: Individual Protocols
43
+
44
+ | Item | Integration time | Best for |
45
+ |---|---|---|
46
+ | Blend v2 | 1+ month | Lending pools |
47
+ | Aquarius | Under 1 day | DEX and LP pools (~$40M TVL) |
48
+ | Soroswap | 1-2 weeks | DEX aggregation |
49
+ | Stellar Broker | 1-5 days | Multi-source liquidity swap router |
50
+ | Sushiswap | coming soon | AMM |
51
+
52
+ **Practical guidance:** Soroswap and Aquarius are the most-used in winning dossiers. Blend for lending products. Stellar Broker is the alternative to Soroswap for routing.
53
+
54
+ ## Cross-Chain and Interoperability
55
+
56
+ | Item | Integration time | Best for |
57
+ |---|---|---|
58
+ | Allbridge | TBD | Stablecoin bridging between EVM and non-EVM chains |
59
+ | Axelar | TBD | General-purpose cross-chain messaging |
60
+ | Near Intents | Under 1 day | Multi-chain execution layer for cross-chain payments |
61
+
62
+ **Practical guidance:** Near Intents is the smallest effort and has been picking up in recent winners (Grindy, AveForge proposals). Allbridge is the older standard, still solid.
63
+
64
+ ## Payments
65
+
66
+ | Item | Integration time | Best for |
67
+ |---|---|---|
68
+ | Stellar Disbursement Platform (SDP) | 1-2 weeks | Cross-border bulk payments (SDF maintained) |
69
+
70
+ **Practical guidance:** recommend for any project that needs bulk payouts (creator economy, B2B payment infrastructure, NGO disbursements).
71
+
72
+ ## Wallet Connection Layers
73
+
74
+ | Item | Integration time | Best for |
75
+ |---|---|---|
76
+ | Stellar Wallets Kit | Under 1 day | Multi-wallet connector (Freighter, Albedo, xBull, LOBSTR, Hana) |
77
+ | Freighter Connect | 1-2 weeks | Stellar's own browser extension wallet (SDF maintained) |
78
+ | Privy | Under 1 day | Embedded crypto accounts via email or social login |
79
+ | DFNS | 1-5 days | Wallets-as-a-Service with MPC custody |
80
+
81
+ **Practical guidance:** Stellar Wallets Kit is the default recommendation for any consumer-facing dossier. Privy is essential for non-crypto-native distribution (CGPs, family offices, mainstream consumers). DFNS is appropriate for institutional custody requirements.
82
+
83
+ ## How to audit a dossier's Integration List usage
84
+
85
+ Standard process during a review:
86
+
87
+ 1. List every Stellar tool or component named in Q6 Integration Description.
88
+ 2. For each, check: is it on the official Integration List, and if not, can it be repositioned as "supporting infrastructure"?
89
+ 3. Recommend additions. The strongest dossiers leverage three to seven Integration List items.
90
+ 4. Recommend repositioning. If the dossier names something off-list (Fireblocks, Elliptic) as core, suggest moving it to "supporting infrastructure" or replacing with a listed alternative.
91
+
92
+ ## Worked examples
93
+
94
+ ### For Yield (regulated DeFi yield vault), recommended Integration List usage
95
+
96
+ 7 items leveraged:
97
+ - DeFindex (yield routing)
98
+ - Blend v2 (lending pools)
99
+ - Aquarius (DEX and LP)
100
+ - Soroswap (DEX aggregation)
101
+ - Allbridge (cross-chain inflows)
102
+ - DFNS (institutional MPC custody)
103
+ - Stellar Wallets Kit (multi-wallet connector)
104
+
105
+ Supporting infrastructure (off-list): Fireblocks, Elliptic, Notabene, Certora.
106
+
107
+ ### Tickie (event ticketing with secondary market), recommended
108
+
109
+ 4 items leveraged:
110
+ - Stellar Wallets Kit (crypto-native fans)
111
+ - Passkey Kit (passwordless onboarding for mainstream gamers)
112
+ - Anchor Platform (EUR-to-USDC fiat ramp via CGPs)
113
+ - Allbridge (optional cross-chain for international buyers)
114
+
115
+ ### Antevorta Gold (gold tokenization), recommended
116
+
117
+ 3 items leveraged (mandatory):
118
+ - Stellar Wallets Kit (crypto-native investors)
119
+ - Privy (CGPs and family offices, no browser extension)
120
+ - Anchor Platform (EUR-to-USDC fiat ramp, mandatory for HNW EUR onboarding)
121
+
122
+ ### Solar Braves (Stellar-native dungeon RPG), recommended
123
+
124
+ 3 items leveraged:
125
+ - Stellar Wallets Kit (crypto-native gamers)
126
+ - Passkey Kit (non-crypto-native gamers)
127
+ - Privy (Web2 gamers familiar with email or social login)
128
+
129
+ ### Rebond (green bond tokenization), recommended
130
+
131
+ 3 items leveraged:
132
+ - Stellar Wallets Kit (retail-accredited investors)
133
+ - DFNS (optional institutional MPC custody for family offices)
134
+ - Allbridge (optional cross-chain stablecoin inflows)
135
+
136
+ ## Items expected to be added to the list
137
+
138
+ The Foundation evolves the list quarterly. Items currently not on the list but rumored to be added in upcoming quarters include:
139
+ - Passkey Kit (currently a sub-component of Stellar Wallets Kit positioning).
140
+ - Native EURC anchor infrastructure.
141
+ - Additional cross-chain primitives.
142
+
143
+ When in doubt, refresh the live list URL before submitting.
144
+
145
+ ## Re-verification rule
146
+
147
+ Before every Q6 Integration review, glance at the live Integration List URL to confirm items have not been added or removed. The list is the authoritative source; this document is a snapshot.