Brief annotation
About the document
Master document and strategic presentation of the development management system SUR-810.
SUR_810_Strategic_Presentation.pptx
Downloading the document...
Integrated Development Management of Russia
KRISTALL741 | STANDARDS 260 | MONETARY AND SETTLEMENT FRAMEWORK 810
The Concept of Transition to the Integrated Development Management System of the Russian Federation
Inter-agency review project
Author: Sergey Leonidovich Sokolov
Version 1.0 | 27 August 2026
DOCUMENT STATUS
Passport concept and mandatory differentiation of terms
| Marking | Value | Status |
|---|---|---|
| SES | Development Management System of the Russian Federation | Designed organizational and methodological system |
| SUR/810 | Soviet ruble in historical lists ISO 4217 | Historical, invalid code |
| RUR/810 | Russian ruble to denomination 1998 | Historical, invalid code |
| RUB/643 | Russian ruble after denomination | The current code of the Russian ruble |
| 810 in account | Technical feature of the ruble in the rules of numbering | Not a valid currency code |
| Outline 810 | Project and registry name of the design outline of the SES | Not currency, not denomination or means of payment |
MAIN
Summary for decision
The Russian Federation has national objectives before 2030 Year and future before 2036 years, strategic planning system, government programs, national projects and budget mechanisms. The challenge for the next phase is not to multiply bodies and documents, but to harmonize goals, data, resources, decisions, risks and measurable results.
SDGs are offered as an organizational, methodological and digital system of integrated development management. The unit of control becomes a closed evidence chain: the goal - the initial state - the solution - the resource - the execution - the result - an independent check - the adjustment.
The operational core of SUR is KRISTALL741: 19 interconnected balance management systems, 13 phases in a decision’s life cycle, and three scales of management. Each of the 741 cells receives a profile covering responsibility, data, resources, risks and results. Layer 260 sets standards, indicators, formulas, sources and validation rules.
Monetary and settlement contour SUR-810 connects the source of financing, the obligation, the ruble payment and the confirmed effect. In the pilot phase 810 is a historical identifier and a registry prefix, not a currency. Money execution and accounting are carried out in RUB/643.
DECISION
Proposed management solution
- Approve the development and limited piloting of SES as a system of decision support and interagency coordination.
- Determine the state customer, coordinator, pilot object and owner of a measurable result.
- Use KRISTALL741 as a methodological addressing model and catalogue 260 as a normative and measurement layer.
- Apply "810" only as the project and registry name of the monetary and settlement circuit; exclude money issue and public exchange promises.
- To offer the Bank of Russia participation in the monetary and legal expertise; to ensure the participation of the Ministry of Finance, the Ministry of Economic Development, the Treasury, Rosfinmonitoring, Rosstandart and interested bodies.
- Following the results of the pilot, submit a legal, economic, technological and organizational assessment and a scaling plan until 2030/2036.
FOUNDATIONS
Strategic and regulatory context
SDS is designed as an applied mechanism for the implementation of already established goals and documents, and not as a parallel contour of public power. The regulatory framework sets goals, mandates and requirements; the SDS itself requires a separate decision on the pilot.
| Basis | What sets | Role for SDGs |
|---|---|---|
| Constitution of the Russian Federation | Powers of the President, Government and Bank of Russia | Non-substitution of institutions and the legality of the monetary contour |
| 172-FZ | Strategic planning system | Linkages of documents, indicators and monitoring |
| Decree No309 | National targets up to 2030/2036 | Top level of goal setting |
| Spatial development strategy No4146-r | Balanced spatial development | Territorial balance sheets and pilots |
| Decree No145 | Scientific and technological development | Forecast, technology and expertise |
| Decree No400 | National security | Limitations, risks and sustainability |
| Resolution No171 | Government Coordination Center | Compatibility with current situation management |
DIAGNOSIS
Problem field: the rupture of the management cycle
The main systemic deficit arises between the strategic planning document and the actually confirmed result. Goals, indicators, budgets, projects, data, risks and reporting often exist in different contours and are updated with different periodicity.
- the same goal is decomposed into disparate indicators and reporting formats;
- the data source, formula, version and owner of the indicator are not always traceable;
- Inter-agency dependencies are detected after the project delay;
- resource solution is not always associated with a specific passport result;
- Risk signals come later than there is a need for adjustment;
- The success of the event replaces the assessment of changes in the state of the territory, industry or person.
TARGET MODEL
Definition of SES and system boundaries
The CSD is a federal organizational, methodological and digital environment that links national goals, 19 balances, data, models, decisions, project obligations, legitimate calculations and evidence of results.
SUR
- collects in a single model the goals, indicators, risks and dependencies;
- forms scenarios and shows the consequences of solutions;
- assigns responsibility through KRISTALL741 module profiles;
- links the resource obligation with the result through the contour SUR-810;
- provides versioning, origin of data and independent verification;
- returns feedback to the next management cycle.
SRS does not comply
- does not make political or legally significant decisions instead of authorized bodies;
- does not create 741 body, 741 information system or new mandatory reporting;
- does not open bank accounts, does not store customer funds and does not transfer money;
- does not issue currency, money surrogate, digital currency or payment token;
- does not replace official statistics, budget accounting and state audit.
ARCHITECTURE
Principles of Integrated Development Management
| Principle | Practical requirement |
|---|---|
| Legality | Every decision, authority and calculation has a legal basis. |
| Federality | The data remains with the owners; The SDS uses harmonized passports and interfaces. |
| Subsidiarity | The decision is made at the minimum sufficient level of management. |
| Balance | The result is evaluated along with resources, limitations and side effects. |
| Evidence | Each indicator has a formula, source, version and validator. |
| Reversibility | For a significant decision, stop conditions, rollback and standby mode are determined. |
| Security | Access, data, models and calculated events are divided into protection classes. |
| Human-centeredness | The result is a change in quality of life and sustainability, not the amount of reporting. |
FIVE WORDS
General architecture of SUR
| Layer | Purpose | Main result |
|---|---|---|
| 1. Normative-target | National objectives, strategies, powers, constraints | Hierarchy of objectives and legal bases |
| 2. Observation and data | Official statistics, departmental data, GASMP, feedback | Verified status picture |
| 3. Analytics and Forecasting | EQUILIBRIUM, balances, scenarios, early signals | Options and implications |
| 4. Project execution | SFERA, ECO-PPA, SPECZASHCHITA, Project Portfolio | Responsible, resources, time frame |
| 5. Calculation and proof | SUR-810, banking/treasury statuses, ESG-IR 1.0 | Relationship of obligation, payment and result |
All layers use the common object identifier and passport version, but retain the legal separation of authority, data, and responsibility.
ARCHITECTURE
Institutional model and power allocation
The SDS is integrated into the existing public administration system. Each institution retains constitutional and legal powers; the digital platform provides coherent information, coordination routes, and evidence package.
| Institute | Role in the circuit | Border |
|---|---|---|
| President of Russia | National objectives and strategic priorities | SDGs do not shape policy decisions |
| Presidential Administration | Coherence of priorities and monitoring of assignments | Departmental execution is not replaced |
| The Russian Government | Portfolio, resources, interagency execution | Legally significant decisions - on established procedures |
| The State Council | Federal and regional coordination | The powers of the subjects of the Russian Federation are preserved |
| Security Council | Risks, safety and sustainability | Access — by modes and tolerances |
| Federal Assembly | Legislation and Parliamentary Control | SES does not replace legislation |
| Bank of Russia | Monetary and payment competence | Participation offered; decisions within independent mandate |
| Russian Treasury | Treasury Execution and Budgetary Traceability | SES does not open or maintain treasury accounts |
| The Accounts Chamber | External state audit | Independent assessment is not replaced by self-assessment |
| Rosstat | Official statistical information | Author's indexes are marked separately |
| Subjects and municipalities | Territorial execution and feedback | The principle of subsidiarity applies |
ARCHITECTURE
Ecosystem of SDGs: roles without duplication
| Component | Function | Result |
|---|---|---|
| EQUILIBRIUM | Balance analysis, forecast and scenarios | Reasonable solutions |
| GASMP | Observation and Early Signals | Confirmed event or rejection |
| KRISTALL741 | Object, phase and scale addressing | Passport of the management module |
| SFERA | Acceptance and routing of initiatives | Transparent offer status |
| ECO-PPA | Structuring of the project and resource commitments | Agreed project package |
| SPECZASHCHITA | Execution and protection of critical processes | Results and Primary Evidence |
| ESG-IR 1.0 | Passport indicator and independent validation | Evidentiary reporting |
| SUR-810 | Relationship of obligation, ruble payment and result | Traceable calculated trace |
A typical chain: GASMP detects a signal → EQUILIBRIUM develops scenarios → KRISTALL741 addresses the module → SFERA registers the initiative → ECO-PPA formalises the project → SPECZASHCHITA ensures implementation → SUR-810 reconciles the obligation and payment → ESG-IR 1.0 confirms the result.
IDENTIFICATIONS
Three codes, three different functions
| Code | Function | What code does not mean |
|---|---|---|
| 810 | Historical memory of calculations and the name of the traceability register | Not valid currency and not value factor |
| 741 | 19 Balance Management Systems × 13 Phases × 3 Scale | Not the number of bodies, departments or mandatory reports |
| 260 | Catalog of standards, indicators, formulas and rules of verification | Not a fixed forever list of regulations |
MONEY AND ACCOUNT CONTOUR
Code 810: historical chronology
| Period / Object | Marking | Correct interpretation |
|---|---|---|
| Soviet Ruble | SUR / 810 | Historical currency designation in the lists ISO 4217 |
| Russian ruble before denomination | RUR / 810 | Historical designation of the old Russian ruble |
| Denomination with 01.01.1998 | 1000: 1 | Complete change in price scale; not the current rate |
| The current Russian ruble | RUB / 643 | Current cash execution and accounting code |
| Bank account number | sign 810 | Technical feature of the ruble according to the rules of the Bank of Russia |
| Project SES | SUR-810 | Name of the resource, obligation, payment and result communication registry |
LEGAL CLEARNESS
810 and 643: Facts, Myths, and Obligatory Disclaimer
| Approval | Evaluation | Correct position |
|---|---|---|
| In Russia, two rubles are circulating - 810 and 643 | Invalid | The current ruble is designated RUB/643 |
| 810 in the account means Soviet rubles | Invalid | This is a technical feature of the ruble in the account structure |
| The amount on the account should be multiplied by 1000 | Invalid | 1000:1 - completed denomination 1998 year |
| ISO-code itself creates a monetary claim | Invalid | The classifier does not create an obligation or a course |
| SUR-810 can be used as project name | Admissible | With a clear disclaimer and calculations only in RUB |
| Conditional unit is possible in the contract | Conditionally | After legal qualification and with a defined ruble performance |
Legal Model
Acceptable use case 810
| Scenario | Risk | Solution for the concept |
|---|---|---|
| Historical symbol and registry name | Low | Apply now with disclaimer |
| Non-transferable Analytical Index | Low-medium | Methodology, audit, no promise of exchange |
| Contractual unit | Medium | Only after the legal conclusion and the model contract |
| Points of the closed project | Medium-high | Do not sell, cash out, promise universal acceptance |
| Multilateral Clearing | High | Not to be included in the base pilot; only with a regulated partner |
| Transferable token or digital right | Very high | A separate regulated project on a legitimate infrastructure |
| Parallel currency "ruble 810" | Unacceptable | Delete from concept |
MONEY AND ACCOUNT CONTOUR
Three-layer model SUR-810
| Layer | Purpose | The Source of Legal Truth |
|---|---|---|
| H-810 - historical | Archive SUR/RUR, comparison of statistical series, documentation of denomination | Primary historical documents and official data |
| L-643 - legal | Contracts, budget obligations, bank and treasury payments | Law, Contract, Bank or Treasury; Amounts of RUB |
| U-SUR - analytical | Optional index of cost, sustainability or result | Approved method; does not change monetary liability |
MONEY AND ACCOUNT CONTOUR
Financial flow and functional modules
| Module | Function | Benchmark |
|---|---|---|
| Sources | Register of budgetary and extrabudgetary sources | Legal basis and limit |
| Obligations | Contracts, stages, amounts, terms | Unambiguous connection to the project |
| Payment calendar | Planning of cash events | Early Deficit Signal |
| Acceptance | Confirmation of stage and result | Set of evidence |
| Decision | Authorization by an authorized person | Signature and authorization |
| Integration | Transfer of Order to Bank or Treasury | Status of execution at RUB |
| Sverka | Comparison of statement and project register | T+1 closure or incident |
| Audit | Unchanged log and unload dossier | The Verified Chain |
The SES operator does not accept client money, does not open accounts and does not make transfers. The money transaction is performed by a regulated infrastructure.
CONTROL
Eight mandatory contours of financial readiness
| Code | Contour | Blocking condition |
|---|---|---|
| LEG | Legal qualifications | Uncertain legal nature of the operation |
| PAY | Payment compatibility | Unlicensed translation or wrong route |
| BUD | Budget compatibility | No limit, basis or treasury control |
| TRC | Cross-cutting traceability | Payment without obligation or acceptance |
| RES | Reserve and liquidity | Inadequate coverage of commitment |
| AML | AML/CFT, KYB/KYC | Undetermined participant or unauthorized signal |
| CYB | Cybersustainability | Violation of authority, integrity or signature |
| CNV | Evaluation and conversion | No approved formula or reliable price source |
OPERATIONAL NUCLEAR
Balance as a management system
In SES, the balance sheet is not a static table or a single indicator. It is a logical control system for a certain area of development: it observes the state of the controlled object, compares it with the target corridor, identifies the causes of deviation, forms impact options, connects the solution with the resource and checks the actual result by feedback.
| System Element | Contents | Mandatory question |
|---|---|---|
| Managed Object | Population, territory, resource, infrastructure, industry or institution | What exactly are we changing? |
| State | Stocks, flows, structure, constraints and inter-balance | Where are we now? |
| Target corridor | Standard, target, tolerance and time frame | Where and within what limits are we going? |
| Observation | Data sources, signals, frequency and quality | How do we know about the change? |
| Model | Causal relationships, scenarios and prognosis | Why did the rejection occur? |
| Regulator | Authorized owner of the decision and the route of approval | Who has the right to make a decision? |
| Impact | Norm, program, project, resource or organizational decision | What exactly will be done? |
| Implementation | Responsible, resource, calendar, dependencies and control | Who, when and at what cost? |
| Feedback | Acceptance, result, independent verification and adjustment | Is there an effect and what to change? |
OPERATIONAL NUCLEAR
KRISTALL741: nineteen balance management systems
| Code | Balance Management System |
|---|---|
| B01 | Demography |
| B02 | Health |
| B03 | Family, income and social well-being |
| B04 | Education, skills and talents |
| B05 | Culture, values and social cohesion |
| B06 | Work and employment |
| B07 | Food and APC |
| B08 | Space and resettlement |
| B09 | Housing and public infrastructure |
| B10 | Transport and logistics |
| B11 | Fuel and energy |
| B12 | Water |
| B13 | Natural capital and ecological capacity |
| B14 | Materials, resources and circularity |
| B15 | Production and cross-sectoral linkages |
| B16 | Finance, investment and budget |
| B17 | Science, technology and innovation |
| B18 | Digital environment, information and data |
| B19 | Security, sovereignty and institutional sustainability |
Each of the 19 systems undergoes the same closed control cycle, but has its own object, target corridor, causality model, set of impacts, decision owners and outcome indicators.
OPERATIONAL NUCLEAR
Thirteen phases of the solution life cycle
| Code | Phase | The main question |
|---|---|---|
| L01 | Signal or need | What's changed? |
| L02 | Identification of data and sources | What is the assessment based on? |
| L03 | Data validation | Can we trust the data? |
| L04 | Base Line | Where do we start? |
| L05 | Balance and Causal Diagnosis | Why did the rejection occur? |
| L06 | Forecast and scenarios | What will happen to different decisions? |
| L07 | Purpose, standard and allowable deviation | What is the result and limit of risk? |
| L08 | Options for solution | What alternatives are available? |
| L09 | Legal Expertise and Security | Is the decision legal and safe? |
| L10 | Resource and calculation model | What resources and calculations are needed? |
| L11 | Implementation and coordination | Who, what and when does it work? |
| L12 | Monitoring, acceptance and validation | Is the test result achieved? |
| L13 | Adjustment, scaling or closing | What to change in the next cycle? |
OPERATIONAL NUCLEAR
Three Scales and Formula 741
| Code | Scale | Model solution |
|---|---|---|
| S1 | National / Federal | National goal, intersectoral balance, federal resource |
| S2 | Regional / Interregional | Territorial scenario and inter-agency portfolio |
| S3 | Municipal / Object / Project | Specific performance, acceptance and effect |
| Example code | Decryption |
|---|---|
| SUR-B16-L10-S1 | Federal resource-calculated model of financial balance |
| SUR-B12-L12-S2 | Regional validation of the water balance result |
| SUR-B06-L11-S3 | Project execution on the balance of work and employment |
KRISTALL741
Universal passport module
| Block | Required fields |
|---|---|
| Identification | Code, name, version, date of action |
| Responsibility | Result owner, operator, matching, validator |
| Legal model | Rules, powers, licenses, permissible and prohibited functions |
| Target and Perimeter | Measurable result, term, territory, participants, restrictions |
| Entrances and exits | Documents, data, events, solutions and exchange formats |
| Indicators | Formulas, sources, frequency, thresholds, exceptions |
| Risks | Legal, resource, financial, social, environmental, cyber risks |
| Dependencies | Related modules, directories, contracts, external systems |
| Decision | What is allowed, warned, blocked and approved by whom |
| Standby mode | Manual scenario, rollback, recovery and stop conditions |
| Evidence | Signatures, extracts, statuses, protocols, hashes and conclusions |
| History | Author, changes, agreement and basis of the new version |
MEASUREMENT LAYER
Catalogue 260: standard for measuring the result
The number 260 stands for Managed Catalog of Standards and Indicators. The catalog is being versioned; each position undergoes methodological, legal and industry verification.
| Group | Contents of passport | Quality control |
|---|---|---|
| Targets | Relationship to national purpose and instrument | Consistency of decomposition |
| Balance sheet | Stock, flow, deficit, sustainability limit | Balanced identity and units |
| Result | Change object state | Not replaced by the volume of activities |
| Risk | Probability, impact, early signal | Threshold and owner of the reaction |
| Data | Source, date, coverage, delay, quality | Origin and version |
| Validation | Verification method, independent validator | Reproducible calculation |
DIGITAL ARCHITECTURE
Registers, data and evidence chain
| Register | Key objects |
|---|---|
| Objectives and documents | Purpose, indicator, reason, deadline, version |
| Balances and objects | Balance, territory, industry, object, relationship |
| Standards and indicators | Formula, source, threshold, validator |
| Signals and initiatives | Event, source, priority, balance system and route |
| Programs and projects | Passport, stage, executor, dependence |
| Resources and funding | Source, limit, assignment, availability |
| Commitments and calculations | Contract, stage, decision, payment status in RUB |
| Risks and Solutions | Signal, Evaluation, Authorized Decision, Term |
| Evidence and results | Acceptance, indicator, verification, conclusion |
| Participants and credentials | Organization, role, power of attorney, admission |
DIGITAL ARCHITECTURE
Management cycle and automation rules
- The signal is recorded with the source, time, territory and level of trust.
- The algorithm offers a linked balance, phase, scale, and route owner.
- EQUILIBRIUM forms the baseline, dependencies, and scenarios.
- Authorized persons choose the decision and fix the legal basis.
- ECO-PPA translates the solution into a project, resource and commitment calendar.
- SUR-810 binds the obligation with the legal ruble performance.
- ESG-IR 1.0 confirms the change in the indicator; the result returns to the model.
| Automate | It requires a human decision |
|---|---|
| Check format, completeness and version | Policy and regulatory choices |
| Comparison of identifiers and dependencies | Resource approval and commitment |
| Calculation of indicators and early signals | Legal qualification of the disputed scenario |
| Blocking Technical Duplication | Addressing critical risk |
| Forming a dossier and reconciliation | Acceptance of results and responsibility |
MEASUREMENT
Result metrics and non-falsifiable readiness
The average score should not hide the blocking risk. Each mandatory circuit receives a level: 0 - blocked; 1 - projected; 2 - admitted to a limited pilot; 3 - ready for scaling.
| Class | Example | Rule |
|---|---|---|
| Stop indicator | Unlicensed transaction, payment without basis | Acceptable value — only 0 |
| Threshold | Completeness of legal qualification | 100% types of operations before pilot |
| Operational KPI | Cricket T+1, availability, STP | The model threshold is specified on the baseline |
| Effect indicator | Change of balance | Comparison with baseline and control scenario |
| Data quality | Completeness of origin and relevance | The source and version are mandatory |
MEASUREMENT
Model KPI financial circuit
Values marked [M] are model parameters of the pilot, not current standards. They are specified after the legal conclusion, the baseline and the first two months of measurements.
| Indicator | Pilot's threshold | Status |
|---|---|---|
| Legal qualification of types of transactions | 100% | Barrier to admission |
| Unlicensed financial functions | 0 | Stop indicator |
| Success of accepted payments | ≥99,0% | [M] |
| Automatic processing without manual editing | ≥90% | [M] |
| Matching to T+1 | ≥99,5% | [M] |
| Duplicate or orphaned payments | 0 | Stop indicator |
| Full chain commitment-result | ≥99,5% | [M] |
| Accessibility of the financial circuit | ≥99,9% | [M] |
| Unauthorized payments | 0 | Stop indicator |
| Formation of a complete dossier, P95 | ≤15 minutes | [M] |
The payment order receives the idempotent key from the obligation, the recipient, the amount, the date, the contract and the stage. Repeat with the same key is blocked before checking.
CONTROL
Safety, AML/CFT and Continuity
| Monitoring | Mandatory requirement | Evidence |
|---|---|---|
| Identification | Participant and Beneficiary Verified Before Operation | File KYB/KYC and status |
| AML/CFT | Signals are reviewed by an authorized compliance officer | Solution and log of actions |
| Credentials | The Two-Person Principle for Monetaryly Significant Actions | EP, role, power of attorney |
| Integrity | Unchanged log of critical events | Signature, time and control hash |
| Access | Minimum privileges and multifactor authentication | Role Matrix and Log Ins |
| Continuity | Standby mode, RTO/RPO and recovery test | Protocol of at least two tests [M] |
| Personal data | Minimization, purpose of processing and storage time | Register of grounds and deletions |
| KII | Classification and profile measures, if applicable | Categorization and control |
IMPLEMENTING
Pilot 2026–2027: Object and limits
The pilot is selected according to the principle of manageable complexity: one complex task or territory, several interrelated balances, measurable results, available data and a ready-made owner of the solution.
| Parameter | Proposed framework |
|---|---|
| Perimeter | 3 projects, 3–5 legal entities and one adjustable payment adapter [M] |
| Operations | Up to 2 000 ruble events; without public issue, exchange and fundraising [M] |
| Balances | The 3–5 most closely connected balances from KRISTALL741 |
| Data | Official and departmental sources plus documented primary information |
| Finance | RUB/643 through a bank or Treasury; "810" only in Registry ID |
| Monitoring | Legal, financial, cybernetic and methodological independent verification |
| Withdrawal | Decision to discontinue, modify or scale |
IMPLEMENTING
Pilot stages: 30 / 100 / 365 days
| Timeframe | Works | Solution of the control point |
|---|---|---|
| 0–30 days | Assignment of the customer and the owner; selection of the object; inventory of law, data, systems and calculations | There is a mandate, borders and a baseline |
| 31–100 days | Legal opinion; model 741; catalogue of indicators; prototype of registers; security architecture | Go/revise/stop for limited launch |
| 101–180 days | Shadow mode without legally significant automatic solutions; reconciliation with current processes | Confirmed data quality and manageability |
| 181–300 days | Limited working pilot with human control and independent audit | Performed stop indicators and KPI |
| 301–365 days | Stress test, recovery, effect assessment and scaling package | Government decision on the next stage |
IMPLEMENTING
KPI Twelve Month Pilot
| Block | Completion criterion |
|---|---|
| Right | 100% Scenarios are Qualified; 0 Unlicensed Functions; 0 Critical remarks |
| Management | 100% critical decisions have owner, basis and evidentiary package |
| Data | 100% required fields have source, time and version |
| Payments | ≥99% Success; ≥90% STP; 0 Losses and losses [M] |
| Sverka | ≥99,5% Operations Closed T+1; unexplained difference — 0 [M] |
| Traceability | ≥99,5% Complete chains; dossier ≤15 Minutes [M] |
| Security | ≥99,9% Accessibility; 0 unauthorized payments; two DR tests [M] |
| Result | Improvement of the selected balance sheet indicator relative to the baseline confirmed |
| Efficiency | Time or labor gain is measured without deterioration of control |
| Audit | Independent legal, financial and cyber verification without critical remarks |
The threshold values [M] are the pilot's hypotheses. The empirical effect is not declared until the baseline and the results of the control period are obtained.
MASSTABING
Road map to 2030 and 2036
| Stage | Focus | Result |
|---|---|---|
| 2026 | Design and legal qualifications | Harmonized architecture, passports and pilot frames |
| 2027 | Pilot and independent inspection | The decision to modify or scale |
| 2028 | Inter-agency integration | Common identifiers, API and evidentiary packages |
| 2029–2030 | Expansion into portfolios and territories | Sustainable cycle of national goals |
| 2031–2036 | Adaptive development management | Scenario management of long-term balance sheets |
ORGANIZATION
Program Management and Responsibility Model
| Role | Responsibility |
|---|---|
| State Customer | Mandate, pilot facility, resource and final decision |
| Interagency Coordinating Council | Dependency resolution and lock control |
| Owner of the result | Change the state of the selected balance |
| Methodical Center | Model 741, catalog 260, quality indicators |
| Platform Operator | Integrations, Availability, Logging and Support |
| Financial operator | Bank or Treasury; executed at RUB |
| Legal Committee | Scenario Qualifications and Border Control |
| Independent Validator | Verification of results, methods and evidence |
| Auditor / Supervisory Authority | Independent evaluation and recommendations |
RISKS
Key risks and management measures
| Risk | Manifestation | Measure |
|---|---|---|
| Legal | SUR-810 is perceived as private money | Disclaimer, qualification, only RUB/643 |
| Reputational | 810 with pseudo-legal theories | Public fact sheet and common terminology |
| Institutional | Fear of organ replacement | Explicit lines of authority and joint management |
| Data | Incomparable formulas and versions | Passport indicator and origin of data |
| Model | Error prediction or automation of the solution | Scripts, person in outline, version log |
| Financial | Payment without reason or double | Set check, two faces, idempotent key |
| Cybernetic | Compromise access or registry | Segmentation, MFA, signature, reservation |
| Project | The first perimeter is too wide. | Limited pilot and stop/go locks |
| Methodical | Activity instead of effect | Baseline and independent validation |
DRAFT DECISION
Draft instruction on pilot launch
Suggested wording for further legal development:
- To the Government of the Russian Federation to prepare proposals for a limited pilot project of the Development Management System of the Russian Federation.
- Determine the state customer, coordinator, pilot object, the list of participants and the owner of the measurable result.
- Provide a distinction between the organizational and methodological architecture of the SRS and the monetary and legal status of the designation 810.
- Form an inter-agency working group with the participation of interested bodies; The Bank of Russia shall offer participation within the established competence.
- Within a period of up to 100 days, prepare a joint legal, financial, technological and organizational conclusion and pilot’s regulations.
- Establish that all legally significant pilot calculations are carried out in rubles of the Russian Federation through authorized banking or treasury infrastructure.
- Within the pilot, do not allow the issue or sale of the instrument identified by code 810 or promises to exchange it; do not allow the operator to perform unlicensed financial functions.
- After twelve months, submit a report with an independent assessment and proposals for termination, finalization or scaling.
PLAN OF ACTION
First 100 days: list of specific results
| Result | Contents | Acceptance |
|---|---|---|
| Pilot's mandate | Customer, owner, facility, boundaries and budgetary basis | Executive document |
| Legal Memorandum | Qualification SUR-810, roles, data and financial scenarios | 0 Open Critical Questions |
| Process Map | Current and target cycle from signal to result | Consent of owners |
| Matrix 741 | Selected balances, phases, scales and passports | Complete required fields |
| Catalogue of indicators | The first version of the set 260 and methods | Expert and statistical verification |
| Data Architecture | Registries, API, identifiers, access and origin | Technical Council |
| Prototype SUR-810 | Register of obligations and payment statuses without storage of funds | Reconciliation of test data |
| Security Model | Threats, Roles, Logging, Backup | Test and report |
| Measurement plan | Baseline, KPI, control script and validator | Independent opinion |
| Gateway solution | Go / revise / stop | Coordinating Council Protocol |
CONCLUSION
Final position
The SRM shifts development management from a set of disparate documents and information contours to 19 interconnected balance management systems and a single but federative cycle of responsibility: from signal and scenario to legitimate resource, execution and independently validated result.
KRISTALL741 creates an addressable operational matrix, catalogue 260 a language of measurement, and SUR-810 traceability of the connection between an obligation, a ruble payment and the result.
Historical accuracy is fundamental: SUR/810 the Soviet Ruble, RUR/810 — the Russian ruble to denomination, RUB/643 — to the current Russian ruble. In a bank account 810 It is a technical feature of the ruble. This history does not create a modern exchange rate or monetary claim.
SUR-810 does not return the old currency - it returns the traceability, long-term and relationship to the result.
ANNEX A
Official sources and regulatory materials
1. Constitution of the Russian Federation, Article 75
2. Federal Law No. 172-FZ "On Strategic Planning in the Russian Federation"
3. Decree of the President of the Russian Federation No. 309 on national goals
4. Spatial Development Strategy, Government Order No4146-r
5. Decree of the President of the Russian Federation No. 145 on scientific and technological development
6. Decree of the President of the Russian Federation No. 400 on the National Security Strategy
7. Decree of the Government of the Russian Federation No. 171 on the Coordination Center
8. Decree of the Government of the Russian Federation No. 1278 on the FIS of strategic planning
9. Decree of the Government of the Russian Federation No. 733 on the national data management system
10. Bank of Russia: explanation of the ruble sign 810 and currency code 643
11. Bank of Russia Regulation No. 809-P: Rules for Numbering Personal Accounts
12. Decree of the President of the Russian Federation No. 822 on denomination
13. ISO: Standard ISO 4217
14. SIX: official escort body ISO 4217
15. SIX: historical list ISO 4217 List Three
16. Bank of Russia: digital financial assets
17. Bank of Russia: digital ruble
ANNEX B
Glossary and rules of terminology
| Term | Working definition |
|---|---|
| Balance management system | Closed circuit: object, state, target, observation, model, solution, impact, resource, execution and feedback |
| Evidence | Document, status, measurement or conclusion with origin and version |
| Contour | A set of processes, data, roles and control rules with a common function |
| Module 741 | Addressable combination of balance, life cycle and scale phases |
| Indicator 260 | Validated passport of definition, formula, source, threshold and verification |
| SUR-810 | Project name of the source, obligation, ruble payment and result communication register |
| RUB/643 | Current designation of the Russian ruble for cash execution |
| Sign 810 | Technical element of the structure of the Russian bank account |
| Pilot | Limited hypothesis testing with predefined boundaries and stop conditions |
| Validator | Independent or functionally separate subject of result verification |
ANNEX C
Methodological reservations
- The document describes the target concept and does not prove the actual economic effect before the pilot.
- The numbers 741 and 260 are elements of the author's architecture; their application requires approved passports and versions.
- Model thresholds [M] are not government regulations, bank rules, or a promise of result.
- Official statistics have priority within their subject area; derived indices are labeled as analytical.
- The algorithm supports decision but does not replace authority, legal responsibility, and professional judgment.
- Financial, tax, accounting, procurement and currency scenarios require separate qualifications for participants and the pilot facility.
- Any function of transferring, storing, exchanging or raising money is excluded from the pilot if it is not performed by a properly regulated entity.
- Scaling is allowed only after an independent assessment of the law, effect, security, cost of ownership and organizational readiness.
End of document
Source materials
Originals and versions of the document
- SUR_810_Master_Document.docxDOCX · main document
- SUR_810_Strategic_Presentation.pptxPPTX · related version
Other editions in web format
Each version is disclosed separately; the sequence of the source document is saved.
SURSUR_810_Strategic_Presentation.pptx · web text+
810
HISTORIC
RCD
Management system
Development of Russia
19 balance management systems • KRISTALL741
Standards 260 • monetary and settlement contour SUR-810
Inter-agency review project
810 is not the pilot's currency
Author: Sokolov Sergey Leonidovich | version 1.0 | 27 August 2026
You can fly now.
MANAGEMENT POSITION
The monetary value of 810 is not introduced - it passes a separate legal gateway
SUR - run as a control system
810 - use only as project code
Organizational and methodological architecture, 19 balance systems, matrix 741, catalog 260 and evidence cycle.
Historical identifier and name of the traceability registry. All calculations, accounting and payments — in RUB/643.
Requested solution: legal training + limited non-monetary pilot
Sokolov Sergey Leonidovich
National goals need a closed execution cycle
THE PROBLEM
Goal
Data
Decision
Resource
Implementation
Evidence
result and deadline
status and signal
Option and Authority
Commitment and limit
Responsible and Stage
effect check
Feedback returns the confirmed result to the next decision cycle
The SES does not create a new power; it makes the current cycle coherent and verifiable.
Sokolov Sergey Leonidovich
Balance is a management system
OPERATIONAL NUCLEAR
Not a static table, but a closed loop of impact and feedback
Object
State
Goal
What we change
Where we are
Target Corridor
Observation
Model
Decision
How we know
Why and what will happen
Who is entitled
Impact
Implementation
Feedback
What we do
Who and what
Has the effect been achieved
object + Objective + surveillance + Model + Authority + Impact + resource + execution + feedback
Sokolov Sergey Leonidovich
Nineteen interrelated balance sheet management systems
KRISTALL741
Man and Society
Territory and life support
Production and capital
Knowledge and sovereignty
B01 Demographics
B07 Food
B14 Resources and Circularity
B17 Science and Technology
B02 Health
B08 Space
B15 Manufacturing
B18 Digital environment
B03 Family and income
B09 Housing and utilities
B16 Finance and investments
B19 Security and Sustainability
B04 Education
B10 Transport
B05 Culture and connectedness
B11 Energy
B06 Labour and employment
B12 Water
B13 Natural capital
Each system has its own object, purpose, regulator, impact and feedback — and is not a new agency.
Sokolov Sergey Leonidovich
SES closes eight management actions
TARGET MODEL
Signal
Diagnostics
Scenario
Decision
Adjustment
Validation
Implementation
Resource
The decision is made by the authorized institute • SRS provides evidence and reversibility
Sokolov Sergey Leonidovich
810
IDENTIFICATIONS
810 / 741 / 260 - three codes, three functions
741
260
TRAVELING
ADDRESS OF MANAGEMENT
MEASUREMENT
Historical memory of calculations and the relationship "resource - obligation - result"
19 Balance Management Systems × 13 Phases × 3 Scale
Catalog of standards, indicators, formulas, sources and validation rules
Codes work together but do not replace each other.
Sokolov Sergey Leonidovich
Code 810 — historical; current ruble — RUB/643
HISTORICAL ACCURACY
SUR / 810
1000: 1
Soviet Ruble
denomination
from 01.01.1998
RUR / 810
RUB / 643
Russian Ruble
Before the denomination
current
Russian Ruble
Historical 1000:1 — a complete change in the scale of prices, not the current exchange rate between "two rubles"
Sokolov Sergey Leonidovich
The four myths about 810 are four verifiable facts
LEGAL CLEARNESS
In Russia, the ruble 810 and 643
The current ruble is designated RUB/643
MYTH
FACT
810 in the account means Soviet rubles
This is a technical feature of the ruble in the account structure
MYTH
FACT
The amount on the account must be multiplied by 1000
1000:1 - completed denomination 1998 year
MYTH
FACT
ISO-code itself creates a monetary claim
The classifier does not create an obligation or a course
MYTH
FACT
810 in a bank account is not an incident and does not require a change of details
Sokolov Sergey Leonidovich
The pilot's money system remains operational
LEGAL BORDER
Ruble
Emissions
Monetary unit of the Russian Federation
Exclusive competence of the Bank of Russia
CFA
The Digital Ruble
Not a means of payment
Form of national currency issued by the Bank of Russia
Pilot: without emission, sale, exchange, wallets and promise of state guarantee
Sokolov Sergey Leonidovich
What is acceptable now, what is conditional, what is excluded
SCENARIO 810
STOP
CAN NOW
AFTER EXPERTISE
NOT IN THE BASIC PILOT
historical symbol
contractual unit
Parallel Currency
Registry Name SUR-810
Defined ruble equivalent
public token or clearing
Non-transferable Analytical Index
Model contract and methodology
promise of exchange and return
Recommended route: historical sign → analytical index → only then separate contractual model
Sokolov Sergey Leonidovich
Three layers - one priority of legal truth
SUR-810
H-810
HISTORICAL REGISTER
RULE
PRIORITY
archive SUR/RUR • comparison of series • Documentation of denominations
In the event of a discrepancy, the law, contract, bank, or Treasury shall prevail in RUB.
The analytical record SUR does not change the monetary liability.
L-643
LEGAL REGISTER
contracts • budget • liabilities • bank and treasury payments RUB
U-SUR
ANALYTICAL LAYER
indices of value, stability or result • only according to the approved method
810 — Memory • 643 — execution
Sokolov Sergey Leonidovich
Money moves into RUB; SAD Drives Evidence
MONEY AND ACCOUNT CONTOUR
Source
Bank /
Treasurer
Outline
Project
account
Acceptance
Decision
Payment
in RUB
Sverka
ESG-IR
Result
SRS
SRS does not comply
Basis • obligation • stage • decision • status • result
does not keep funds • does not open accounts • does not transfer money
Transfer operator - only regulated bank or Treasury
Sokolov Sergey Leonidovich
Readiness is equal to the weakest mandatory circuit
CONTROL
Right
Payment
Budget
Next
LEG
PAY
BUD
TRC
legal qualification
Regulated route
Limit and basis
End-to-end traceability
Reserve
AML/CFT
Cyber
Evaluation
RES
AML
CYB
CNV
Coverage of obligations
KYB/KYC and signals
Integrity and Access
Approved method
Readiness SUR = min ( LEG, PAY, BUD, TRC, RES, AML, CYB, CNV )
Sokolov Sergey Leonidovich
Address of each management task
KRISTALL741
MANAGEMENT SYSTEMS
BALANCES
THE PHASE OF LIFE
CYCLA
MASSTABA
GOVERNANCE
object and target state
from signal to adjustment
Federal • Regional • Project
19 × 13 × 3 = 741
741 — not the number of bodies or IT systems; this is the number of management modules addressed
Sokolov Sergey Leonidovich
Thirteen Phases Turn Signal Into System Training
KRISTALL741
L01 Signal
L02 Sources
L03 Verification
L04 Base line
OBSERVE
L05 Diagnosis
L06 Scripts
L07 Purpose / Standard
L08 Options
L09 Law / Security
DECIDE
L10 Resource model
L11 Execution
L12 Validation
L13 Adjustment
PERFORM AND STUDY
Phase L13 returns the confirmed result in L01 - the system becomes adaptive
Sokolov Sergey Leonidovich
One Balance System - Three Scale Solutions
KRISTALL741
FEDERAL
national target • intersectoral balance • federal resource
REGIONAL
territorial scenario • interagency portfolio
PROJECT
specific performance • acceptance • confirmed effect
SUR-B16-L10-S1
financial balance • resource model • federal scale
Scales are related by feedback: the project result clarifies the regional and federal model
Sokolov Sergey Leonidovich
Eight components form one proof route
ECOSYSTEM
GASMP
EQUILIBRIUM
KRISTALL741
SFERA
Signal
script
Address
Initiative
ECO-PPA
SPECZASHCHITA
SUR-810
ESG-IR 1.0
draft
execution
calculated trace
Validation
Each component is responsible for its own function; a common identifier links the evidence
Sokolov Sergey Leonidovich
Authority remains with the existing bodies
INSTITUTIONAL MODEL
Objectives and strategy
Coordination
Russian President • Federal Assembly • Government of the Russian Federation
Presidential Administration • State Council • Coordination Center
Money and Execution
Security and independence
Government • Ministry of Finance • Treasury • regulated bank
Security Council • Bank of Russia — participation within its own mandate
Data and methodology
Control and proof
Rosstat • RAS • industry centers • subjects of the Russian Federation
The Accounts Chamber • Audit • Independent Validators
The SRM links the basis, data, decision, resource and result - but does not make a decision instead of the institute
Sokolov Sergey Leonidovich
100
IMPLEMENTING
Pilot 30 / 100 / 365 days - with the right to stop
365
DAYS
DAYS
DAYS
Mandate and boundaries
Legal Gateway
Verified result
customer • object • reference line
conclusion • passport • prototype
Pilot • Audit • Scale Decision
Perimeter [M]: 3 Project • 3–5 legal entities • to 2 000 Ruble Operations
Each control point allows go/revise/stop
Sokolov Sergey Leonidovich
100%
MEASUREMENT
Pilot proves right, reliability and effect
≥99% [M]
Legal Qualification of Scenarios
Unlicensed Functions
success of accepted payments
≥99,5% [M]
≥99,9% [M]
full chain and reconciliation T+1
availability of financial contour
Confirmed balance effect
[M] — pilot's model threshold, not a state standard and not a promise of effect
Sokolov Sergey Leonidovich
Stop/go gateways protect the pilot from irreversible errors
RISKS
STOP
public promise of exchange or return
legal model approved for 100% scenarios
receiving other people's money by the operator SUR
all payments go through a bank or Treasury
no power, reason or AML-permit
the decision has an owner and a full evidentiary package
broken signature, integrity or access control
Recovery and safe rollback
810 is used as a valid currency
No independent review criticisms
Law and security are barriers, not elements of the average score
Sokolov Sergey Leonidovich
Road map to 2030 and 2036
MASSTABING
2026
2028
2031–36
Design
Integration
Adaptive management
Right • Architecture • Base Line
common identifiers • API •
scenarios • Early Signals • Long-term balance
2027
2029–30
Pilot
Extension
limited run • independent check
portfolios • territories • national goals
Scaling is determined by the readiness of the gateways - not by a calendar date
Sokolov Sergey Leonidovich
Four Actions to Launch an SAR
DRAFT DECISION
Approve the limited pilot of SES
To appoint the customer and the owner of the result
Decision Support and Interagency Coordination Systems
identify the object, boundaries, participants and control points
100 days to complete the legal gateway
After 12 months to make a decision
810 — project name only; financial performance — RUB/643
stop • revise • scale based on independent verification
SUR-810 does not return the old currency - it returns the traceability, long-term and relationship to the result
Sokolov Sergey Leonidovich
Sources indicated in the presentation 26
- Author's concept of SUR, Sokolov Sergey Leonidovich, version 1.0, 27.08.2026.
- https://www.cbr.ru/explan/acts_bko/
- [/Sources]
- Author's concept of SUR, version 1.0, 27.08.2026.
- https://kremlin.ru/acts/constitution/item
- https://kremlin.ru/events/president/news/73986
- https://publication.pravo.gov.ru/Document/View/0001201406300016
- Author's concept of SUR: "Balances as control systems", Sokolov Sergey Leonidovich, 27.08.2026.
- The author’s KRISTALL741 classification, version 1.0, 27.08.2026.
- The author’s concept of SUR and KRISTALL741, version 1.0, 27.08.2026.
- https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html
- https://www.kremlin.ru/acts/bank/11299/print
- https://www.cbr.ru/Queries/XsltBlock/File/144005/-1/2400-2401
- https://www.cbr.ru/finm_infrastructure/digital_oper/
- https://www.cbr.ru/PSystem/dr/
- https://pravo.gov.ru/proxy/ips/?doc_itself=&fulltext=1&nd=102033239&page=1&rdk=155
- Author's model SUR-810, version 1.0, 27.08.2026.
- Author's model of financial readiness SUR-810, version 1.0, 27.08.2026.
- The author’s KRISTALL741 model, version 1.0, 27.08.2026.
- The author's architecture of the ecosystem of SUR, version 1.0, 27.08.2026.
- https://publication.pravo.gov.ru/Document/View/0001202102220029
- Author's plan of the pilot of SUR, version 1.0, 27.08.2026.
- Author's register KPI Pilot SUR-810, Version 1.0, 27.08.2026.
- Author's risk matrix of SUR, version 1.0, 27.08.2026.
- https://www.cbr.ru/counteraction_m_ter/
- Author's road map of SUR, version 1.0, 27.08.2026.



