Platform
1foundation world faq
Institutional context for foundation world faq begins in Inflation Regime Effects on Family Portfolios: Regional Cost Curve Comparison and continues in Heritage Restoration Funding Models: Risk Controls Worth Documenting. What follows concentrates on foundation world faq, not introductory platform mechanics.
What is Foundation and why does it exist
1Foundation is a perpetual capital platform connecting allocators, operators, and builders across New York, Israel, and Ukraine with documented governance rather than vintage fund calendars. The platform exists to compound trust and execution capability across decades instead of clearing quarterly deployment targets. Regional hubs such as Foundation Israel, Foundation Ukraine, and Foundation Incubator carry corridor specific mandates while sharing committee standards, refusal logs, and privacy rules described elsewhere on this site.
Foundational purpose and committee architecture appear in What Is Foundation and Why It Exists, which this FAQ summarizes for first time readers rather than replacing.
Fiduciary conduct guidance from the U.S. Securities and Exchange Commission investment resources helps family offices explain why perpetual capital disclosure rhythms differ from vintage fund reporting they may know from home markets.
How do I start working with Foundation
1Engagement typically begins with a mandate fit conversation, corridor selection, and documentation of allocator governance requirements before any bilateral file opens. Principals should expect onboarding questionnaires, conflicts disclosure, and privacy acknowledgments rather than immediate deal flow. Operators and builders follow parallel paths through regional hubs with artifact or asset specific gates.
Step by step onboarding detail appears in How to Start Working With Foundation, which expands the summary above with committee contact paths and document checklists.
How is Foundation different from a traditional fund
1Traditional funds organize around vintage lifecycles: raise, deploy, harvest, return, repeat. Foundation organizes around permanent partnership intent, tranche unlock memos tied to proof quality, and refusal categories logged for allocator audit. Pacing follows artifact depth or asset governance milestones rather than LP reporting calendars that reward activity counts over relationship continuity.
Human capital programs hosted through Foundation Incubator apply the same non expiring logic upstream, where exploration may run years before incorporation becomes relevant.
Which corridors and regional hubs does Foundation cover
1Privacy and data handling
Foundation collects allocator onboarding records, operator rosters, pass logs, and incubator correspondence under written privacy standards that define retention, redaction, and destruction timelines. Data room access logs should not outlive the transaction they support without policy authority. Allocators evaluating bilateral expansion should read privacy standards before sharing principal identifying information.
Operational privacy detail appears in Our Commitment to Data Privacy, which specifies scope, tiers, and corridor application.
Corporate governance research from the OECD corporate governance research supports committee memos that explain why privacy and conflicts policies belong in minutes before capital moves.
Who makes investment and refusal decisions
1Investment and refusal authority sits with documented committee structures rather than with individual relationship managers acting informally. Recusal, related party logs, and pass categories should appear in minutes allocators can audit. Regional hub operators execute within mandate bounds set by platform governance essays rather than improvising pacing from broker pressure alone.
Team background and governance links appear on About Us, which this FAQ supplements with process answers rather than biography alone.
What should allocators expect on pacing and reporting
1Reporting emphasizes proof events, refusal rationale, and milestone integrity rather than deployment percentages alone. Allocators should expect measured pacing when artifact or asset files require additional diligence, even when macro cycles compress behavior elsewhere. Quarterly activity counts are not treated as proof of mandate quality when relationship depth and documentation standards lag. Principals who need faster cadence should compare whether mandate fit actually matches vintage liquidity expectations before requesting exceptions platform governance cannot support.
Macro research on long horizon allocation from the International Monetary Fund publications helps family offices justify non vintage pacing in home market committee minutes.
Where do operators and builders find corridor detail
1Operators and builders should start with the regional hub that matches their mandate: Foundation Israel for Israeli real estate execution, Foundation Ukraine for Kyiv repositioning and reconstruction files, Foundation Incubator for upstream technology companionship. Platform level essays explain how hubs connect; hub level essays explain phase gates, checklists, and operator standards field teams actually use.
Corridor specific questions often appear first on the FAQ hub pages before they reach platform level onboarding. Field notes and launch announcements publish on regional hub blogs as mandates evolve.
Minimum capital and mandate fit questions
1Foundation does not publish universal minimum ticket sizes because mandate fit depends on corridor, governance requirements, and bilateral structure rather than on a single threshold. Principals should expect fit conversations to cover allocator committee process, conflicts standards, and timeline patience before any file opens. Operators and builders encounter parallel gates through regional hubs with artifact or asset specific requirements. Family offices often begin with corridor selection memos that document home market counsel expectations before any principal identifying data enters onboarding files.
Perpetual capital philosophy essays in the General archive explain why fit precedes scale rather than treating onboarding as a subscription form alone.
Conflicts of interest and allocator protection
1Foundation publishes conflicts standards that require disclosure when operator, introducer, or mentor relationships intersect investment authority. Allocators should read conflicts and privacy essays before sharing principal identifying data through onboarding channels. FAQ answers here point to policy memos rather than replacing bilateral disclosure schedules counsel must review.
Conflicts policy detail appears in platform governance essays indexed alongside privacy standards in the General archive.
Bank for International Settlements cross border banking statistics, available through the Bank for International Settlements, help committees explain corridor exposure when monetary cycles overlap related party concentration.
