Unauthorized WOPI host. Please try again later and report to your administrator if the issue persists.
$8M project breaking ground in Redmond, OR. $1B pipeline incoming. Follow this channel to watch us build live and claim your prelaunch airdrop.
Star Wars launch — May 4
This page is the public record of material policy changes, clarifications, and corrections.
Its purpose is simple: when SKOpi makes a meaningful governance, treasury, token, project-status, or disclosure change, that change should not disappear into scattered posts or informal explanations. The handoff places a Material Policy Updates Log in the recommended public disclosure stack, alongside the entity, board, treasury, token-rights, utility, project-progress, and proof pages.
SKOpi’s transparency model is not supposed to be improvised or hype-driven. It is supposed to be policy-based, stage-accurate, and honest about what is active versus what is only planned. A Material Policy Updates Log supports that by creating one official place to record meaningful changes over time.
This page also supports a core handoff principle: transparency includes correcting mistakes, not just publishing polished pages.
A material update is any change or clarification that could reasonably affect how the public understands:
This log is not for every tiny edit. It is for changes that matter to public understanding or reliance.
A strong version of this page should track updates across a few clear categories.
These include things such as:
The handoff specifically notes that major board changes are event-driven items appropriate for transparency updates.
These include things such as:
The handoff says treasury-control claims are among the public statements that should generally receive internal review before publication.
These include things such as:
The handoff explicitly calls out major token policy changes as event-driven updates and says token-rights statements, token utility changes, and redemption-value statements should generally trigger internal review.
These include things such as:
The handoff says project disclosures should be factual, date-specific where possible, and not misleadingly final when still contingent.
These include:
The handoff recommends that SKOpi aim for a predictable transparency cadence where practical.
The suggested cadence is:
These are the core standing pages, such as governance summary, token-rights disclaimer, treasury framework summary, board structure summary, and entity structure summary.
These may include monthly or quarterly governance, treasury, or project summaries, along with major policy updates when adopted and material project milestone updates when appropriate.
These include major board changes, major treasury policy changes, major token policy changes, major project acquisitions or exits, and major governance incidents where disclosure is appropriate.
This page should mainly capture the second and third categories.
The handoff is very clear that public transparency content should not be improvised casually.
Depending on the subject matter, public disclosures should be reviewed by some combination of:
High-risk public statements should receive elevated review.
So this page should function as an approved record, not just a blog feed.
A new entry may be triggered when:
This approach fits the handoff’s position that official public statements should come from authorized sources and go through review when risk is high.
A clean public entry format should include:
Date
When the update became effective or was posted.
Category
Governance, Treasury, Token Policy, Project Status, or Correction.
Title
A short label for the update.
Summary of Change
A brief explanation of what changed.
Why It Matters
A plain-English explanation of why the public should care.
Status Label
For example: planned, approved, active, corrected, superseded.
Linked Documents
The official page or policy summary that now controls.
This structure fits the handoff’s repeated emphasis on clarity, date-specificity, and separation between planned and active matters.
One of the most important uses of this page is correction.
If materially inaccurate public statements are made by company personnel, directors, officers, affiliates, or public-facing partners, SKOpi should have the right to:
This page is a natural place to record those corrections so the official record stays clear.
The handoff also says affiliate and ambassador language should align with official policy documents, and should not inaccurately claim that:
If affiliate or community language needs correction, this page can log the clarification and point readers back to the controlling official documents.
This page should not become:
Its job is to log material changes and clarifications, not to create new informal policy.
A clean opening could be:
This page records material policy updates, clarifications, and corrections in SKOpi’s public governance and transparency framework.
It is intended to help readers track meaningful changes over time, including updates to governance posture, treasury policy, token policy, project-status disclosures, and official public clarifications.
A live entry could look like this:
[Month Day, Year] — Token Policy Update
Title: Clarification to Token Utility Language
Summary: SKOpi updated its public token utility language to better distinguish between active utility, planned utility, and aspirational long-term concepts.
Why it matters: This change helps prevent public confusion and keeps token-rights communications aligned with official company policy.
Status: Active
See also: Token Utility & Redemption Summary; Token Holder Rights Disclaimer
That style matches the handoff’s emphasis on plain-English clarity and stage-accurate disclosures.
In simple terms:
This page is the official public log of major SKOpi policy updates and corrections.
It should track meaningful changes in governance, treasury, token policy, project disclosures, and public clarifications.
It should use dated, plain-English entries.
And it should reinforce that official policy changes are reviewed and recorded, not left to scattered posts or vague community messaging.
This page is where SKOpi shows the public the difference between claims and proof.
The handoff places a Proof / Transparency Page inside the recommended public disclosure stack, alongside the governance, treasury, token-rights, utility, tokenomics, and project-progress pages. It is intended to support a public posture that is transparent, but not reckless.
The purpose of this page is not to hype.
It is to give the public a clean place to verify the core things SKOpi says about itself, at the level that is appropriate for a public-facing website.
That means this page should help people confirm:
The handoff gives a very clear SKOpi-specific transparency posture.
At a high level, SKOpi should publicly present itself as:
This page should act as the “evidence hub” for that posture.
A strong SKOpi proof page should show the public the documents and checkpoints that support the core governance story.
This section should point to the public explanation of the company structure, including the parent-and-operating-company framework.
Suggested support items:
This helps show that SKOpi’s entity story is structured, not improvised.
This section should point to the pages that explain how founder control and board oversight fit together.
Suggested support items:
This is important because the handoff repeatedly emphasizes that SKOpi should not fake decentralization.
This section should explain the policy-level treasury-control model.
Suggested support items:
The handoff specifically supports describing treasury protection at a policy level without exposing keys or sensitive security details.
This section should point to the documents that make clear what SKOPI does and does not represent.
Suggested support items:
This is one of the most important things this page should clarify.
This section should show the standard allocation reference.
The current approved token allocation reference is:
Required note set:
This section should not just state the numbers. It should show that the tokenomics reference is being treated consistently across the public materials.
This section should point to the page that explains where the project stands and how proceeds are intended to be used at a category level.
Suggested support items:
This helps prevent the public from confusing plans with completed execution.
The handoff is very clear that transparency should not become recklessness.
So this page should not expose:
The public should understand the framework, but not receive an operational map that increases risk.
This page should also clarify that official policy statements come from authorized company sources.
The handoff’s recommended spokesperson classes are:
It also says that directors, advisors, affiliates, and community members should not be treated as authorized to define company policy unless expressly approved.
That matters on a proof page, because it helps visitors understand what counts as official.
The handoff also says SKOpi should require that affiliates, marketers, and community participants do not inaccurately state that:
This page is a good place to reinforce that the official docs control over community hype.
The handoff says certain public statements should generally trigger internal review before publication, including:
This means the proof page should be built from approved materials, not live speculation or casual social language.
A clean live version of this page could be organized like this:
A short summary of the governance and transparency posture.
Links to:
This matches the handoff’s recommended public disclosure stack.
The allocation table and required notes.
A clean label system such as:
This follows the handoff rule that planned items should not be presented as active.
A note that only approved company statements and official pages control.
A section showing corrections, clarifications, or material updates when needed.
The handoff explicitly says transparency includes correcting mistakes, not just posting polished materials.
A clean opening statement for the live page could be:
SKOpi is committed to policy-based transparency.
This page collects the public documents, tokenomics references, and governance summaries that explain how SKOpi is structured, what SKOPI tokens are and are not, how major oversight works at a high level, and what parts of the project are active versus still planned. SKOpi aims to be transparent without exposing security-sensitive details or overstating rights, utility, or project status.
In simple terms:
This page is the public proof hub for SKOpi.
It should connect the official governance, treasury, token-rights, utility, tokenomics, and progress pages in one place.
It should reinforce that SKOpi is founder-controlled with real oversight, that tokens are not corporate shares, and that public claims must match approved policy.
And it should provide transparency without exposing the kinds of details that would create security risk.
This page is meant to explain two things clearly:
The handoff places this page in the core public disclosure stack, alongside the entity, board, treasury, token-rights, and token-utility pages. It is part of the broader rule that SKOpi public transparency should be policy-based, honest, and careful not to overstate what is active versus what is only planned.
SKOpi is not supposed to rely on vague marketing language.
The handoff says public claims should match the real legal structure, governance framework, and activation status of the project. It also says that if something is planned but not active, it should be labeled that way. This page exists to do exactly that for project status and proceeds usage.
At a high level, SKOpi is being built as:
The current established core structure is:
The handoff repeatedly stresses that SKOpi should distinguish between:
That same rule should control this page.
So project updates should not present an idea, future intention, or working concept as though it is already fully live and operational.
A clean way to describe SKOpi’s progress is through simple status categories.
This includes things like:
This category is already strongly reflected in the handoff and governance pack.
This includes things like:
The handoff says some of this is already consistent with the framework, while parts still require more specific implementation and rollout language.
This includes things like:
The handoff’s committee framework makes clear that land execution is a real tracked category and should be reviewed through the development oversight process.
Public progress updates should not imply:
This is one of the main reasons this page matters.
The handoff does not frame transparency as “publish every sensitive detail.”
Instead, it supports policy-level disclosure that is honest and useful without becoming reckless. That same approach should apply to use-of-proceeds. The public should understand the categories and logic of intended use, while sensitive treasury-security details and internal execution mechanics can remain non-public.
A clean SKOpi use-of-proceeds summary should generally describe proceeds at a category level.
Proceeds may be used for foundational company buildout such as:
This aligns with the handoff’s emphasis on building a real governance and controls stack.
Proceeds may be used for:
These uses match the chartered role of the Treasury, Audit & Controls Committee.
Proceeds may be used for:
The handoff makes clear that platform utility and redemption mechanics require approved implementation, not improvisation.
Proceeds may also be used, where approved, for:
This matches the handoff’s separation between HoldCo governance and OpCo/project execution.
One of the most important points in the handoff is that money, expenses, and liabilities should sit where they actually belong.
It specifically notes examples such as:
So a strong use-of-proceeds page should explain not just broad categories, but also that proceeds are expected to be routed through the appropriate entity and treasury structure.
The handoff also says that certain funding movements should trigger formal review, including:
That means use-of-proceeds is not supposed to be treated as one loose wallet pool. It is supposed to work within the entity map and treasury-approval framework.
A useful public progress page should describe progress in milestone form, such as:
This fits the handoff’s broader theme that public communications should be accurate, staged, and tied to what is actually happening.
A clean public statement for this page could be:
SKOpi is being built in stages.
Current work includes governance and treasury architecture, legal and entity structure, token-policy and transparency framework development, platform and ecosystem preparation, and land-development execution planning through the appropriate operating entities. Proceeds are intended to be used across these categories as approved, with funds routed through the appropriate treasury bucket and legal entity rather than treated as one undifferentiated pool.
That framing matches the handoff better than aggressive, over-specific promises.
In simple terms:
This page should tell people where SKOpi stands and how proceeds are broadly intended to be used.
It should separate active work from planned work.
It should explain that proceeds may support governance, treasury controls, platform buildout, token-system rollout, and land-development execution.
And it should make clear that money is supposed to be routed through the right entity and treasury structure, not handled casually.
SKOpi uses a fixed token allocation framework designed to be clear, consistent, and policy-based.
This page is meant to serve as the public single-source summary for token supply, bucket allocation, bucket purpose, and the most important use restrictions. The handoff file explicitly says this Tokenomics Summary should function as the standard reference across the public pack, the internal pack, and the future agent framework.
The current standard total supply of SKOpi is:
1,000,000,000 SKOPI
This is the working reference supply for governance, transparency, and tokenomics packaging.
The approved token allocation breakdown is:
The simple working breakdown is:
This shorter version can be used in public explainers as long as it stays consistent with the full allocation above.
The handoff is clear that each token bucket has a different purpose and should not be casually blended into the others. Tokenomics is not just about the total number of tokens. It is also about maintaining discipline around what each bucket is actually for.
500,000,000 SKOPI
50% of total supply
The Treasury bucket is the primary strategic reserve of the SKOpi ecosystem.
It is intended to function as the main war chest for:
The Treasury bucket is not just a generic token stash. Material movements, reallocations, or policy changes affecting the Treasury bucket should be treated as governance-sensitive actions.
200,000,000 SKOPI
20% of total supply
The Public Sale bucket is intended for the structured public token sale process.
It is tied to the SKOpi tranche sale framework and is the primary bucket used for:
The Public Sale bucket is specifically linked to the sale ladder structure and should not be treated as a general-purpose discretionary pool. Any material change to how this bucket is used should be treated as a token-governance issue.
100,000,000 SKOPI
10% of total supply
The Founders bucket is intended for founder allocation and founder-related long-term alignment. The handoff describes it as reflecting the founder’s strategic role in creating, controlling, and building the SKOpi structure.
The Founders bucket should remain distinct from Treasury, Public Sale, Liquidity, and Community / Rewards. That separation matters for transparency and governance credibility.
100,000,000 SKOPI
10% of total supply
The Liquidity bucket is intended for:
This bucket is for DEX liquidity and market structure, not general spending. It should not be treated as a casual reserve for payroll, admin spending, unrelated treasury patching, board compensation, or general operating expenses. The handoff specifically says this rule should be stated clearly in both internal and public-facing materials.
100,000,000 SKOPI
10% of total supply
This bucket is intended for community-facing and ecosystem distribution activity, including airdrops, rewards, incentive structures, and related participation mechanics. The handoff also specifically states that the Community bucket includes affiliate token bonuses.
When this bucket is described publicly, affiliate token bonuses should not be omitted where relevant, because that is part of the approved purpose of the bucket.
The handoff repeatedly treats the following as the key interpretive notes that should stay attached to SKOpi tokenomics:
These are not side comments. They are part of the standard reference.
The handoff says public materials that discuss treasury, community rewards, affiliate bonuses, liquidity, public sale, founders, token utility, or token distributions should either:
That rule exists to prevent drift and inconsistency across the site and governance materials.
The handoff also gives examples of bad tokenomics packaging. Public materials should not:
Consistency matters here.
This Tokenomics Summary does not by itself activate token utility or define wallet execution rules.
The handoff says:
So this page defines the tokenomics structure, not every operational rule around it.
SKOpi has a 1 billion token supply.
It is split like this:
And the four most important notes are:
That is the standard public tokenomics reference for SKOpi.
SKOpi’s transparency model is designed to be honest, structured, and security-aware.
That means we want the public to understand how SKOpi is structured, how decisions are governed, how token rights are limited, and how treasury protections are framed at a policy level. At the same time, we do not believe transparency requires publishing operational details that would create security risk.
For SKOpi, transparency does not mean improvising public claims.
It means publishing clear, consistent explanations of:
The purpose is to help the public understand the real framework without turning internal controls into a public operating manual.
The handoff is clear that SKOpi should be transparent, but not reckless.
That means:
For example, SKOpi may publicly describe treasury protections, multisig architecture, and governance review at a high level, while still withholding private key details, signer-security procedures, and sensitive internal controls.
The public transparency posture should generally cover:
That is the posture the handoff describes as credible and defensible.
The handoff also warns against overstating public claims.
SKOpi should not inaccurately state that:
This applies not just to the company, but also to affiliates, marketers, public-facing partners, and community promoters.
A core transparency rule is that public claims must match real policy.
That includes public statements about:
These are not supposed to be handled through casual off-the-cuff posting. High-risk public statements should receive internal review before publication.
Transparency also requires clarity about who is authorized to define company policy publicly.
The recommended official spokesperson classes in the handoff are:
Directors, advisors, affiliates, and community members should not be treated as authorized to define company policy unless they are expressly approved to do so.
One of the most important transparency rules is that SKOpi should clearly distinguish between:
If something is planned but not live, it should be labeled that way. If a feature is approved in principle but not operational, public language should not present it as fully active. This matters especially for token utility, redemption, treasury features, and project status claims.
The handoff says SKOpi should maintain both:
Public materials are meant to help outsiders understand the structure at a high level.
Internal materials are meant to guide actual approvals, conflicts review, authority mapping, treasury execution, signer workflows, and governance discipline. That split is intentional.
Transparency also includes correcting mistakes.
If materially inaccurate public statements are made by:
SKOpi should be able to:
The point is not just to publish polished materials, but to keep public language accurate over time.
Because public transparency often touches token supply, treasury, rewards, liquidity, and token distribution, the standard tokenomics reference should be treated as controlling.
That standard reference is:
Important related notes:
When public materials refer to token buckets or token use, they should either include this block or reference the official Tokenomics Summary.
The handoff recommends a public-facing transparency stack that includes:
This is meant to create a public governance library that is understandable, credible, and consistent.
SKOpi token utility is designed to be real, limited, and clearly defined.
That means the token may have meaningful uses inside the SKOpi ecosystem, but those uses are not supposed to be described as automatic, unlimited, or unconditional. The handoff is very clear that token utility must be expressly defined, governance-approved, and communicated accurately.
SKOpi tokens are ecosystem tokens, not corporate shares.
Any utility, redemption feature, or program right must be:
No one should assume a right exists just because it was discussed, mentioned aspirationally, or expected by the community.
The handoff groups SKOpi utility into several categories:
Use of tokens within SKOpi programs, community structures, affiliate systems, or platform interactions.
Use of tokens for rewards, distributions, stipends, referrals, affiliate incentives, loyalty mechanics, and similar program features.
Use of tokens for approved value-credit mechanisms, such as applying tokens toward a permitted purchase or transaction under company rules.
Use of tokens for non-binding signaling, participation, ranking, or other limited ecosystem input processes.
Use cases approved later, such as gated access, rewards tiers, community programs, feature unlocks, discounted ecosystem services, priority access, or other platform functions.
As of the current draft stage, the distinction is:
SKOpi is intended to support:
No specific utility should be treated as fully active unless the company has:
In other words, SKOpi should clearly distinguish between:
SKOpi may support a redemption or checkout-credit framework, but only under explicit company-approved rules.
The redemption model should be described as a conditional company program, not an automatic cash-equivalent right. That means redemption may:
The key concept already discussed in the handoff is:
SKOpi may potentially be usable for up to 25% of a property purchase price or similar approved real-estate transaction amount, subject to program rules.
A previously discussed version of the framework included a $1 credit value per SKOpi when used in that approved purchase context.
That concept should be treated as:
It must be separately documented and activated before it should be treated as live.
Unless separately approved and expressly stated in writing, SKOpi does not automatically give token holders the right to:
Redemption utility, if offered, is a program right, not an unrestricted withdrawal right.
Any approved redemption framework may be conditioned on factors such as:
Where redemption is tied to a real-estate transaction, SKOpi may impose a cap.
The leading discussed framework is that token redemption or credit may apply to up to 25% of an approved purchase amount. This cap exists to:
Unless changed by approved governance, redemption should never be described as covering the full purchase price.
SKOpi’s redemption or credit utility may depend on actual inventory, project, or transaction availability.
This means:
This point is important and should always be disclosed clearly.
Before full redemption utility is activated, SKOpi may still be used for:
These uses are easier to activate than a real-estate-linked redemption framework and may come online earlier.
The handoff also says SKOpi may be used for:
It may also serve as a governance-alignment incentive for:
Even in those cases, the token still does not automatically become corporate equity.
The company may allow token holders to participate in:
Unless expressly stated otherwise, those rights are:
SKOpi utility should never be described as guaranteeing:
Utility is not the same thing as a guaranteed return.
Because this page talks about token utility and distribution logic, it should include the standard token allocation reference:
Required notes:
SKOpi token governance is designed to be structured, limited, and honest.
That means the token is part of the SKOpi ecosystem, but it is not supposed to be described in ways that blur the line between token utility and corporate ownership. The handoff is very clear that token governance should be handled through written policy, consistent public disclosures, and board-level oversight for material changes.
In the SKOpi framework, token governance means the rules around:
It does not mean that token holders automatically govern the corporation. The handoff repeatedly separates token rights from shareholder rights and board rights.
SKOpi’s token governance is intended to sit primarily at the SKOpi Global Holdings level, not inside the operating land-development entity.
That structure is important because token policy, token treasury, and public token disclosures are treated as top-level governance matters, while the land-development entity is supposed to focus on execution. This separation also matches the broader entity-structure logic in the handoff.
A central rule of SKOpi token governance is that holding SKOPI does not automatically make someone:
The handoff’s token-holder disclaimer is explicit that token ownership does not automatically equal stock ownership, equity rights, liquidation rights, board rights, or corporate governance rights.
If token holders have rights, those rights must be expressly defined in writing.
The handoff says token rights may include things like:
But none of that should be assumed unless the company has actually approved and published it.
Token governance also depends on a single standard tokenomics reference.
The current standard allocation is:
The handoff also says that whenever a document talks about treasury, community rewards, affiliate bonuses, liquidity, public sale, founders, token utility, or token distributions, it should either include this allocation block or reference the official tokenomics summary.
The token buckets are not supposed to be treated as interchangeable.
The handoff specifically says:
That means token governance is not just about how many tokens exist. It is also about making sure each bucket is used consistently with its stated purpose.
The handoff is clear that token utility is not supposed to be improvised casually.
Material changes to:
must go through the proper governance process. Management is not supposed to make major token changes informally.
A major part of SKOpi token governance is the redemption framework.
The handoff says any redemption system may be conditioned on things such as:
That means redemption should be described as conditional and program-based, not automatic or unlimited.
The leading redemption framework discussed in the handoff is that token redemption or credit may apply to up to 25% of an approved purchase amount in a qualifying real-estate transaction. The handoff also says this cap exists to preserve business economics and should not be described as covering the full purchase price unless governance formally changes it.
The handoff also makes a critical point: redemption utility may depend on actual inventory or approved transaction availability.
So:
This is an important part of token governance because it keeps public promises tied to real operational capacity.
The token may still have governed utility even before a full real-estate redemption system is fully active.
The handoff lists examples such as:
This means SKOPI can have real utility before the most ambitious redemption use cases are fully live.
The company may later allow token holders to participate in things like:
But the handoff says those rights are generally non-binding, advisory, and not corporate governance rights unless expressly stated otherwise.
Another important token-governance rule is that utility should not be described as a guaranteed financial outcome.
The handoff says SKOPI should never be described as guaranteeing:
That protects the public description of the token from drifting into claims the governance framework does not support.
No public statement should materially conflict with the token-governance framework.
The handoff specifically warns against things like:
Consistency is part of token governance.
In simple terms:
SKOPI is part of the SKOpi ecosystem, but it is not the same thing as corporate equity.
Token holders do not automatically own the company or control the board.
Any real token rights have to be clearly defined in writing.
Token utility, redemption rules, and tokenomics must stay consistent with approved policy.
And major changes to token rights or utility should go through real governance approval, not casual management decisions.
SKOpi treasury is designed to be controlled, separated, and reviewable.
The core idea is simple: treasury should not operate as one undifferentiated wallet. Different categories of funds should be held in separate buckets, with different approval paths, different signer structures, and different levels of oversight depending on the risk involved.
This is part of the broader SKOpi model of founder-led execution with real internal controls, independent oversight, and transparency.
Treasury oversight exists to help prevent a few major problems:
The treasury framework is meant to support discipline, not just access. Technical wallet access does not equal permission to act.
SKOpi’s treasury philosophy is that assets should be separated by function.
That means:
This separation is a governance feature, not just an accounting preference.
The treasury framework divides assets into distinct buckets, each with its own purpose.
This is the day-to-day working treasury.
It covers ordinary business needs such as:
This bucket is for the most sensitive real-estate movements.
It covers:
This bucket is intended for token-market and liquidity activity.
It covers:
This is the preservation bucket.
It is meant for:
This bucket supports ecosystem distribution activity.
It covers:
Each bucket exists so that one category of activity does not casually consume or compromise another.
SKOpi’s treasury oversight also depends on having different multisig structures for different types of funds.
The Ops treasury is structured as 3-of-5.
This wallet is intended for ordinary treasury operations and approved routine payments. The policy intent is to preserve business continuity without creating extreme friction for every normal expense. Neutral involvement is preferred but is not mandatory for every routine operating payment.
The Acquisition treasury is structured as 2-of-3.
The approved signer design is:
This structure is intentionally tighter because land and escrow movements are more sensitive. The operating principle is that high-risk acquisition actions should not function like a one-person treasury. The two founder keys should not function like the same key in two places.
The Liquidity treasury structure is not fully finalized yet.
The placeholder options are:
Until that structure is formally approved, no liquidity-wallet setup should be treated as final, and material deployment from this bucket should receive elevated board review.
Treasury signers are also categorized by role, which helps define why they are included and how they are expected to behave.
Examples include Iosif Key A and Iosif Key B.
These signers represent founder-controlled authority, but they are still expected to operate under policy and approval rules.
Examples include a neutral CPA, neutral attorney, or other governance-approved independent signer.
These signers exist to strengthen control and credibility.
These may include finance/control signers or other approved treasury-function roles.
They support treasury operations, but they should not have uncontrolled strategic authority.
Treasury actions are not all treated the same.
They are meant to follow the Reserved Matters framework.
Examples include:
These can be handled through approved operating authority.
This level applies to standard treasury-planning and policy items that are more than routine but not extraordinary.
This level is meant for items such as:
This level is meant for the most sensitive matters, including:
The point is to match stronger controls to higher-risk decisions.
The treasury framework also includes draft threshold guidance.
For the Ops / General Treasury:
For the Acquisition / Land / Escrow bucket, land-related disbursements should not be treated as routine just because funds are available. Major property commitments should generally be escalated to Level C or Level D.
For the Liquidity Treasury, until finalized, all material movements should be treated as Level D.
For the Community / Rewards / Distribution Treasury, routine approved distributions may be operational, but extraordinary or policy-changing distributions should require Level C or Level D review.
Treasury oversight also requires a formal replacement path for signers.
If a signer becomes:
the board may replace that signer through formal process.
The current approved timing concept is that around 7 business days of unavailability or unresponsiveness can trigger replacement review and signer rotation. Replacement should include written reasons, appropriate approval, a wallet-rotation plan, updated records, and post-rotation security confirmation.
Treasury oversight is not just a wallet issue. It is also a committee issue.
The Treasury, Audit & Controls Committee is intended to oversee:
The Governance, Ethics & Conflicts Committee is intended to review treasury matters where:
This helps make sure treasury decisions are not just technically approved, but also governance-clean.
Treasury rules also apply to compensation.
Payments to directors, officers, affiliates, insiders, Freddy Jewell, founders, family-linked recipients, or related entities are not supposed to be treated as routine merely because a wallet can technically send them. They must follow the approved compensation framework, documented approval routes, and conflict/recusal rules where applicable.
Likewise, token stipends or token-based compensation for independent directors, Freddy Jewell, officers, or advisors must come only from the approved treasury/distribution bucket and follow approved terms, including vesting or lock rules where applicable.
Major changes to treasury architecture are treated as elevated matters.
That includes changes to:
These are generally treated as Level D matters.
No person is supposed to use SKOpi treasury assets for:
Any suspected misuse should trigger internal review, record preservation, governance/conflicts review if needed, and board escalation where material.
In simple terms:
SKOpi treasury is supposed to be divided into separate buckets, not run as one loose wallet system.
Routine operations should not control all funds.
Land money should be protected separately.
Liquidity activity should face elevated review.
Major treasury moves should require stronger approvals.
Signer roles and replacement rules should be formal.
And having technical access to a wallet should never be treated as the same thing as having authority to act.
SKOpi is designed to be founder-controlled with real oversight.
That means control at the shareholder level remains with the founder, while the Board exists to provide actual review, discipline, and accountability on major matters. The handoff file is very clear that the Board is meant to be real, not decorative, and that independent oversight should not be marketed in a fake way.
At a high level:
This structure is meant to avoid two bad extremes:
The intended balance is straightforward: founder-led, but with real board process around important decisions.
The Board is expected to oversee major governance, treasury, token, and conflict-sensitive matters.
That includes oversight of:
The handoff also states that token governance is intended to sit primarily at the HoldCo level, which makes Board oversight especially important there.
The Board is not supposed to micromanage daily operations.
Its role is oversight, authorization, and review, not running every executive task. Officers remain responsible for execution and management. The handoff specifically says day-to-day execution remains with officers and management.
The Chair helps lead meetings, shape the agenda, coordinate with committee chairs, and make sure important matters are escalated properly.
But even if the Chair is also the CEO, that does not erase independent oversight. The handoff is explicit that the Chair must still respect:
In other words, meeting control is not supposed to override governance discipline.
SKOpi’s governance framework includes a Lead Independent Director role to strengthen the credibility of oversight.
This role is intended to help:
The handoff emphasizes that this role should be substantive, not decorative.
Independent directors are expected to actually review matters, ask hard questions where needed, and help preserve governance credibility.
They are not supposed to function as passive approvals. The handoff states plainly that an independent director should not be called “independent” while acting only as management’s echo.
The handoff describes three standing committees that may support Board-level oversight:
Focuses on treasury, controls, financial discipline, and multisig-related review.
Focuses on conflicts, ethics, governance compliance, and policy integrity.
Focuses on major land/project review, feasibility, and project-stage oversight.
These committees exist to deepen review, not eliminate Board accountability.
Treasury governance is a Board-level issue.
The Board is expected to ensure treasury governance is real and documented, including oversight of:
Committees and officers may support this work, but the Board retains ultimate oversight responsibility.
Because token governance is intended to sit mainly at the HoldCo level, the Board should oversee the policy framework around the token.
That includes:
This is important because SKOPI is not supposed to be described in ways that conflict with the actual legal structure.
The Board is also responsible for making sure conflicts are handled properly.
This includes matters involving:
Where needed, the expected tools are:
That conflict discipline is a major part of what makes the oversight framework credible.
The handoff specifically notes that Freddy Jewell is planned as a dual-purpose:
Because that creates a dual-role situation, Freddy should not be presented as a purely independent director. Matters involving Freddy’s compensation, authority expansion, special grants, reimbursement exceptions, related-party arrangements, or board-seat renewal should follow special conflict and approval discipline.
The Board framework also includes executive sessions and recusal rules.
Independent directors should be able to meet without management present when appropriate, especially for founder-sensitive matters, compensation review, governance concerns, and conflict matters.
Directors are also expected to recuse themselves when a conflict materially impairs objective review. The handoff specifically notes that recusal events should be documented by the Secretary.
One important Board responsibility is making sure public governance descriptions are materially accurate.
That includes public statements about:
The Board is expected to prevent public overstatement, especially around decentralization or rights that do not actually exist.
In simple terms:
SKOpi is not trying to fake decentralization.
The founder controls the company at the shareholder level.
The Board exists to provide real oversight on governance, treasury, token policy, conflicts, and major structural decisions.
Independent directors, committees, recusal rules, and executive sessions are part of making that oversight meaningful.