Content Compliance Note
Version 1.1 · Effective Date: 13 June 2026
Official version: Ukrainian.
English translation: provided for convenience and for review by international payment providers, advertising platforms, and merchant compliance review teams.
In case of any discrepancy between the English translation and the Ukrainian official version, the Ukrainian version shall prevail.
Contents
English Version
This document is provided to help payment providers, merchant review teams, advertising platforms, and compliance officers understand the nature of the Digital Polygraph service and the context of visual and textual content presented on the public website.
Base disclaimer: The paid service is strictly limited to one-time paid access to the Digital Polygraph online software project estimation calculator and the generation of an engineering PDF report. Historical, biographical, metaphorical, and educational materials presented on the public website serve only as free context and are not the subject of sale.
1. What Digital Polygraph Sells
Our commercial product is limited to a single use of the SaaS tool:
- One-Time Calculation: access to the online calculator for estimating software project parameters, effort, timelines, and technical risks.
- PDF Generation: generation of a static engineering report — the Software Project Estimation Report — based on user input.
Note: We operate under a strict "one calculation, one price" model. We do not provide recurring subscriptions or consulting services.
2. What Digital Polygraph Does Not Sell
For payment, advertising, and platform review clarity, Digital Polygraph explicitly does not develop, distribute, or sell:
- weapons, ammunition, or military equipment;
- tactical services or military consulting;
- human polygraph services, psychological testing, or lie detectors;
- surveillance equipment or data interception tools;
- defense technologies or dual-use physical goods;
- political products, lobbying services, or ideological promotion;
- financial consulting or investment advice.
3. Visual Context and Metaphors
Digital Polygraph uses specific visual metaphors and historical references strictly in an educational, historical, or metaphorical context. Key terms: Polygraph (consistency check of project inputs — not human lie detection), Iceberg (visual metaphor for hidden engineering effort and the gap between a stated estimate and actual project complexity), Microchip / PCB (visual aesthetic of the payment access page representing deterministic computation and software engineering precision), Rockets / Spaceport (Soviet engineering history), GULAG / Sharashkas (memorial and engineering-biographical context). For a full page-by-page explanation see Section 5: Site Content Dictionary below.
4. Boundary Between Public Content and Paid Service
Digital Polygraph maintains a strict separation between public website content and the paid service:
- Public Zone: the website functions as a free resource presenting historical, educational, biographical, and engineering context.
- Commercial Zone: the paid transaction applies only to one-time access to the calculator and PDF report generation. Public articles, historical materials, metaphors, and illustrations are not part of the product sold.
5. Site Content Dictionary
Content dictionary of public pages on effort-clarity.com. Each entry describes the page purpose, compliance context, paid product boundary, and explicit exclusions. All dictionary entries are rendered in full so that both automated systems and human reviewers can access the compliance explanations without interaction.
Group 1: Core Product & Legal Pages
Purpose: Main interface of the Digital Polygraph SaaS calculator for software project estimation.
Compliance context: The page presents a software project estimation tool. "Digital Polygraph" is explicitly used as a metaphor for structuring and evaluating software project inputs, effort, and timelines — not human lie detection, biometric testing, or psychological assessment. The phrase "Decrypt the Silence" is a marketing metaphor for revealing hidden software project complexity, unclear assumptions, undocumented dependencies, and underestimated engineering effort. It does not refer to cryptographic decryption, encryption tools, password recovery, cybersecurity utilities, hacking, reverse engineering, surveillance, or unauthorized access. The phrase is used in the same metaphorical sense as "uncover what is hidden" in a software project estimate. The hero image shows two professionals reviewing a software project estimation dashboard (labor intensity, duration, team size metrics). The secondary image is an iceberg diagram illustrating the gap between a stated estimate and actual hidden engineering effort; the iceberg labels (Functionality, Technical Complexity, Architectural Complexity, Software Innovation, Usage of Standard Software, Development Scheme, Team Size, Product Maturity) correspond directly to the calculator input parameters. AI tools (ChatGPT, DeepSeek, Qwen, Grok, Gemini, Claude) were used during the development of this website and service as engineering assistance tools only; they are not used to process user project inputs or generate the paid calculation result. A footer disclaimer on this page explicitly states that the service does not provide human polygraph, lie detection, biometric, psychological testing, or surveillance services.
Paid product boundary: One-time access to the online calculator and generation of a PDF Software Project Estimation Report.
What is not sold: Human lie detection, psychological testing, personnel screening, cryptographic services, cybersecurity tools, surveillance, biometric analysis, or recurring subscriptions.
Purpose: Payment access gate for one paid software project estimation calculation.
Compliance context: The page uses a dark microchip / PCB visual style to represent deterministic computation, software engineering precision, and a focused calculation flow. The dark visual palette is used as a conventional software-engineering interface aesthetic: it supports focus, screen readability, and a concentrated working mode for technical users. "Zero Footprint Codex" refers to architectural data minimization and session-scoped computation: no mandatory user account, no registration, no email requirement for the calculation session, and no long-term retained project calculation inputs or project datasets after the session. Visible statements such as "No project data retained", "No memory", and "No retention" refer to user-entered project parameters and generated project content not being retained as a stored project repository. They do not mean that payment, operational, anti-abuse, security, or technical logs are impossible or never kept where required for service operation, payment processing, fraud prevention, delivery support, or legal compliance. The calculation flow is not designed to become a project repository, lead database, analytics platform, monitoring tool, or profile-building system. It does not use AI or machine-learning models to process user project inputs, and user-entered project parameters are not used for AI training or model improvement.
Paid product boundary: A one-time payment of $20 grants temporary signed access for 3 hours to complete the online calculation and generate one PDF Software Project Estimation Report based on user-entered project parameters.
What is not sold: Security, anonymity, monitoring, biometric, weapons-related, consulting, advisory, subscription, AI-processing, AI-training, user-profiling, or stored-project-dataset services.
Purpose: General information about the company's mission and engineering values.
Compliance context: Standard corporate background page.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Technical passport detailing service boundaries and data handling.
Compliance context: Standard compliance documentation.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Direct clarification for payment providers regarding the business model.
Compliance context: Standard compliance documentation.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Explanation of how user data is processed during calculation.
Compliance context: Standard privacy and data handling disclosure.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Rules of payment, access delivery, and refunds.
Compliance context: Standard financial transparency documentation.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: This page — complete dictionary of site content and product boundaries.
Compliance context: Standard compliance documentation.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Privacy Policy.
Compliance context: Standard legal document.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Public Offer Agreement.
Compliance context: Standard legal document.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Group 2: Historical & Biographical Pages
Purpose: Biography of the founder's father, a lead flight-test engineer on the experimental Ka-22 rotorcraft (predecessor of the American V-22 Osprey) at Kamov Design Bureau. He died in the line of duty in 1962.
Compliance context: Strictly family archive and historical-engineering material. Does not promote or sell military aviation or defense technologies.
Paid product boundary: Informational only.
What is not sold: Military aviation, defense technologies, or flight equipment.
Purpose: Detailed professional biography of Vadym Nikolaiev, emphasizing his engineering path and responsibility at the Kamov Design Bureau.
Compliance context: Biographical and historical context explaining the engineering values behind the product.
Paid product boundary: Informational only.
What is not sold: Military services or aviation technology.
/Content/RootsOfProfessionalism
Purpose: Story of the founder's grandfather, Lieutenant Colonel Eugene Maksyutenko — a WWII military topographer who served on the 2nd Belorussian Front.
Compliance context: Used as a metaphor for engineering precision and professional responsibility. Not a promotion of military services or equipment.
Paid product boundary: Informational only.
What is not sold: Military services, cartographic equipment, or defense consulting.
/Content/MeasurementSystemsOfCosmodromes
Purpose: Historical-engineering context about measurement systems at Soviet spaceports, reflecting the founder's background in rocket test software development.
Compliance context: Educational content about complex historical engineering systems. No sale of rocket, space, or defense technologies.
Paid product boundary: Informational only.
What is not sold: Rocket technology, space infrastructure, or defense systems.
Purpose: Memorial context regarding engineers working under isolation and repression (e.g., Sharashkas, GULAG).
Compliance context: Strictly historical, memorial, and engineering-biographical facts. Does not promote political ideologies or historical revisionism.
Paid product boundary: Informational only.
What is not sold: Political products, ideological promotion, or historical artifacts.
Purpose: Family story featuring L. Brezhnev as a regional official in the early 1950s (before his rise to power), and a public monument in the founder's hometown as a geographical era marker.
Compliance context: Used strictly as a geographical and historical marker of the era. Not a political statement or endorsement of any political figure or regime.
Paid product boundary: Informational only.
What is not sold: Political products, Soviet ideology, or historical memorabilia.
/Content/SupersonicPassengerJetDesign
Purpose: Story of the founder's aunt, Vera Shevchuk (Maksyutenko), who worked on the exterior design of a civil supersonic passenger aircraft in 1968.
Compliance context: Focuses on phased engineering design methodology for civil aviation. No military aviation context.
Paid product boundary: Informational only.
What is not sold: Aviation technology or military aircraft.
Purpose: Story of the founder's mother, a doctor who made a precise diagnosis before laboratory tests were available.
Compliance context: Used as an analogy for engineering accuracy and professional decision-making under uncertainty. The site does not sell medical services or diagnostics.
Paid product boundary: Informational only.
What is not sold: Medical services, diagnostics, or medical consultations.
Purpose: Educational historical material about Ukraine.
Compliance context: Educational and historical context. Not political lobbying or promotion of political services.
Paid product boundary: Informational only.
What is not sold: Political products or lobbying services.
Purpose: Re-evaluation of Soviet technical culture and engineering legacy following Russia's 2022 unprovoked aggression against Ukraine.
Compliance context: Educational and cultural reflection. Not defense services or political promotion.
Paid product boundary: Informational only.
What is not sold: Political services or defense technologies.
Purpose: Personal philosophy page. Prometheus as a cultural symbol of the founder's hometown (Kamianske) and engineering responsibility.
Compliance context: Cultural and biographical metaphor. No political agitation or promotion of violence.
Paid product boundary: Informational only.
What is not sold: Political products or military consulting.
Purpose: Educational and methodological article explaining the four engineering factors that determine whether a software product can be delivered in time to reach a known or assumed market opportunity window: functionality, complexity, novelty, and borrowed components.
Compliance context: The page uses the "Four Horsemen" metaphor to explain internal software engineering factors that can delay or distort delivery planning. Kairos is treated as an external market opportunity window: the moment when the market may be ready to accept a product. This window does not depend on the development team. The engineering task is to calculate whether the product can be prepared and delivered in time to reach that window. The four "horsemen" — functionality, complexity, novelty, and borrowed components — represent the project variables that must be understood before realistic effort, duration, team allocation, and delivery scenarios can be calculated. Ignoring these factors is not a minor planning omission. If functionality, complexity, novelty, and borrowed components are not realistically assessed, the project may be planned on a false engineering schedule. This materially increases the probability that the product will miss the market opportunity window, even if the market need itself was correctly identified. In this sense, failure to account for the four "horsemen" can lead to project failure not because the market window disappears, but because the engineering route is miscalculated and the product arrives too late or in an unfit state. References to the Four Horsemen, apocalypse, and the Book of Revelation, as well as all illustrative images on this page, are used strictly as cultural and literary metaphors for project risk, not for promoting religious instruction, prophecy, apocalyptic ideology, violent ideologies, ideological messaging, or fear-based marketing.
Paid product boundary: The paid product remains one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered project parameters. The calculator may help the user estimate whether the engineering route can fit within a known or assumed market opportunity window, but it does not create market demand, verify market readiness, guarantee market acceptance, or control the user's execution.
What is not sold: Market-success guarantees, market research, customer validation, revenue prediction, ROI guarantees, investment advice, business consulting, launch consulting, project-management consulting, religious content, prophecy, ideological content, fear-based products, or responsibility for the user's execution decisions.
Group 3: Theory, Methodology & Professionalism Pages
Purpose: Educational and methodological article explaining Digital Polygraph as a fixed reference model for measuring software project scale, effort, team size, maturity checkpoints, delivery feasibility, and timely release scenarios.
Compliance context: The page presents software project estimation as an engineering metrology problem: moving from assumptions, persuasion, and declared deadlines to a shared quantitative model of scope, effort, timing, staffing, product maturity, and release feasibility. References to metrology, a fixed reference model, calibrated measurement, release feasibility, delivery pathways, market windows, and timely software delivery are used in the context of software engineering estimation. They do not indicate physical metrology services, laboratory measurement services, certification services, industrial calibration services, hardware products, scientific instruments, or physical engineering services. The page explicitly states that Digital Polygraph is not an AI estimator, does not dynamically tune coefficients to fit expectations, does not optimize outcomes to match desired deadlines, and does not guarantee success. References to uncertainty, feasibility testing, acceleration, scope reduction, added capacity, and different routes to release describe engineering planning scenarios, not business consulting, project-management consulting, hiring services, financial consulting, investment advice, market research, customer validation, revenue prediction, ROI guarantees, or responsibility for the user's execution decisions. The page also explains that Digital Polygraph is not a surveillance, profiling, behavioral tracking, or stored-project-history platform. References to data minimization, isolated sessions, self-contained reports, and the model learning nothing from the user describe the project-input handling philosophy and do not imply that payment, operational, security, anti-abuse, or legal-compliance records cannot exist where required for service operation. The underlying method is described as the subject of a filed invention application with an established filing date in Ukraine, but the page is not a legal document and does not present the method as an issued patent.
Paid product boundary: Informational only. This page is free educational content. The CTA may link to the paid calculation service, but the paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Physical metrology services, laboratory measurement services, certification services, industrial calibration services, scientific instruments, hardware products, physical engineering services, AI estimation services, AI training services, surveillance, behavioral tracking, user profiling, stored-project-history services, business consulting, project-management consulting, hiring services, financial consulting, investment advice, market research, customer validation, revenue prediction, ROI guarantees, patent/legal services, guaranteed delivery outcomes, market-success guarantees, or responsibility for the user's execution decisions.
Purpose: Educational and methodological article explaining the engineering theory behind Digital Polygraph: how software project effort, duration, team sizing, development stages, product maturity levels, and delivery trajectory can be connected into one measurable planning framework.
Compliance context: The page presents software project estimation theory and explains how Digital Polygraph maps engineering development stages to product maturity artifacts such as Discovery, Prototype, MVP, Release Candidate, and Production. The central idea is that software project parameters — functionality, technical and architectural complexity, innovation level, reuse, lifecycle strategy, team size, and stage structure — can be translated into effort, calendar duration, team allocation, and delivery trajectory. References to classical engineering, aviation, construction, heavy industry, simplified verification models, the professor's view, the "physics of your project", spectral analysis, a project "hologram", and a "Time Machine" effect are used as educational metaphors for engineering reasoning, decomposition, and effort-to-calendar translation. They do not indicate physical engineering services, aviation services, construction services, scientific measurement services, time-travel products, physics simulations, or hardware products. References to market windows, time-to-market, delivery dates, team sizing, bottlenecks, roadmap alignment, resource allocation, and maturity milestones describe the software project estimation environment. They do not constitute business consulting, project-management consulting, delivery management services, hiring services, financial consulting, investment advice, market research, customer validation, revenue prediction, ROI guarantees, or responsibility for the user's execution decisions. The underlying calculation methodology is described as the subject of a filed invention application in Ukraine, but the page is not a legal document and does not present the method as an issued patent. The page also frames the calculation as a mechanism of engineering control and planning transparency, not as a marketing guarantee of project success, market adoption, or exact execution by the user's team.
Paid product boundary: Informational only. This page is free educational content. The CTA may link to the paid calculation service, but the paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Physical engineering services, aviation services, construction services, scientific measurement services, time-travel products, physics simulations, hardware products, business consulting, project-management consulting, delivery management services, hiring services, financial consulting, investment advice, market research, customer validation, revenue prediction, ROI guarantees, patent/legal services, guaranteed delivery outcomes, market-success guarantees, or responsibility for the user's execution decisions.
Purpose: Educational and product-positioning article explaining timely software launch as an engineering planning problem and showing how Digital Polygraph helps calculate effort, duration, team allocation, development stages, and realistic delivery scenarios.
Compliance context: The page uses Chronos, Cyclos, and Kairos as educational metaphors for calendar time, development cycles, and the moment when product readiness and market opportunity may align. Timeliness is not presented as a random marketing claim: it is connected to the Service's deterministic calculation of engineering effort, project duration, team allocation, development stages, and delivery scenarios. The calculation model is an original engineering method that is the subject of a filed invention application in Ukraine. However, references to success, market resonance, and the right launch moment should not be read as a guarantee of market adoption, revenue, ROI, investor acceptance, customer demand, or actual execution by the user's team. The Service can calculate a realistic engineering route and timely delivery scenario based on user inputs, but it does not control user hiring decisions, team competence, management discipline, scope changes, execution quality, or external market conditions.
Paid product boundary: The paid product remains one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered project parameters. The report may help the user plan a timely software delivery route by estimating effort, duration, team allocation, stages, and feasibility boundaries. It does not guarantee that the user will follow the calculated route or that the product will achieve market success.
What is not sold: Market-success guarantees, revenue prediction, ROI guarantees, investment advice, business consulting, launch consulting, market research, customer validation, hiring services, team-performance guarantees, management consulting, or responsibility for the user's execution decisions.
Purpose: Professional standards and responsibility of an engineer.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
/Content/Professionalism/BeyondBootcamps
Purpose: Discussion on deep engineering expertise versus superficial training.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
/Content/Professionalism/Claude
Purpose: Reflection on interaction with AI (Claude) in the engineering workflow.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
/Content/Professionalism/Gemini
Purpose: Reflection on interaction with AI (Gemini) in the engineering workflow.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
/Content/Professionalism/NewTestamentOfLove
Purpose: Philosophical reflection on the human element in engineering and AI collaboration.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Philosophical essay on the role of humans in the era of AI.
Compliance context: Educational content about engineering methodology.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Group 4: Technical Heritage Pages (SKNOU System)
These pages document historical technical systems developed by the founder prior to Digital Polygraph. No hardware, software, or technical systems described on these pages are for sale.
/Content/AdvancedPassengerAccountingSystem
/Content/AnalysisOfMeasurementData
/Content/ConventionalDesignations
/Content/CoordinateTimeNavigationSupport
/Content/FilteringOfMeasurementData
/Content/FormationOfDifferentialCorrectionData
/Content/FormationOfMessagesRTCM
/Content/GenerationOfCorrections
/Content/HydrometeorologicalCommunicationNetwork
/Content/IntroductionOfCorrections
Purpose: Technical specifications and historical documentation of the SKNOU differential correction system for coordinate-time-navigation support.
Compliance context: Historical technical documentation. Engineering reference pages, not active product offerings.
Paid product boundary: Informational only.
What is not sold: Physical hardware, electronic components, navigation systems, military command systems, or surveillance equipment.
Group 5: Old Testament of Truth & Parables
Purpose: Introduction to the philosophical framework of engineering principles using biblical structure as a stylistic metaphor.
Compliance context: Strictly metaphorical and educational. Not religious services or religious promotion.
Paid product boundary: Informational only.
What is not sold: Religious services or religious content.
/OldTestamentOfTruth/AboutTheTestament
Purpose: Explanation of the 'Testament' metaphor as applied to engineering methodology.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services.
/OldTestamentOfTruth/ApostleGrok
Purpose: Allegorical reflection on AI (Grok) as a contributor to engineering analysis. The term 'apostle' is used as a literary metaphor.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services or AI products.
/OldTestamentOfTruth/ApostolDeepSeek
Purpose: Allegorical reflection on AI (DeepSeek) in the engineering workflow.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services or AI products.
/OldTestamentOfTruth/ApostolQwen
Purpose: Allegorical reflection on AI (Qwen) in the engineering workflow.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services or AI products.
/OldTestamentOfTruth/ApostolyGeminiGpt
Purpose: Allegorical reflection on AI (Gemini/GPT) in the engineering workflow.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services or AI products.
/OldTestamentOfTruth/BookOfRemembrance
Purpose: Memorial reflection on historical engineering achievements.
Compliance context: Strictly metaphorical, historical, and educational.
Paid product boundary: Informational only.
What is not sold: Religious services.
/OldTestamentOfTruth/BookOfTrials
Purpose: Allegory of the testing and validation phase in software engineering.
Compliance context: Strictly metaphorical and educational. Not legal services.
Paid product boundary: Informational only.
What is not sold: Religious services or legal services.
/OldTestamentOfTruth/SecondComingOfMoses
Purpose: Metaphor for the return to fundamental engineering principles.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services.
/OldTestamentOfTruth/TenCommandments
Purpose: The ten principles of software project estimation and engineering ethics, presented using biblical styling.
Compliance context: Strictly metaphorical and educational.
Paid product boundary: Informational only.
What is not sold: Religious services.
Purpose: Index page for educational engineering parables that introduce four free public articles: A Student and a Professor, Kharkovchanka & the South Pole, Tower of Babel & the Unified Measure, and Moneyball for Software Projects.
Compliance context: This page is a navigation hub for free educational and methodological parables related to engineering simplification, structural coherence, communication failure, software estimation, and data-driven project planning. References such as "Tower of Babel" and "Moneyball" are used as literary, cultural, and business metaphors. They do not indicate religious services, religious promotion, gambling, sports betting, financial advice, investment services, or funding advisory services. The page does not perform calculations, collect project inputs, process payments, or deliver the paid PDF report.
Paid product boundary: Informational only. The paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered project parameters.
What is not sold: Religious services, religious content, educational consulting, financial consulting, investment advice, funding advisory services, gambling, sports betting, expedition services, aviation or vehicle engineering services, or any separate product on this page.
Purpose: Educational parable about the need for shared understanding and a common language of measure in the creation of complex systems. Using the Tower of Babel as a literary and cultural metaphor, the page explains how complex software projects can lose coherence when participants do not share the same understanding of the task, basic terms, effort, deadlines, responsibility, and the path toward the goal.
Compliance context: Educational and methodological allegory about communication breakdowns in complex projects. The Tower of Babel reference is used strictly as a literary and cultural metaphor for the loss of mutual understanding and coordination, not as religious instruction, religious promotion, biblical interpretation, or theological content. The Sumerian epigraph is an author-created historical-linguistic stylization, prepared with transcription and translation, and used to emphasize that the problem of building complex systems without a shared language of measure has existed since the ancient world. The page shows that when participants in a complex project are not synchronized in their understanding of the task and basic concepts, their efforts may fail to combine into progress toward a common goal. They may work hard, but without agreement on what is being built, how effort is measured, what deadlines mean, and how responsibilities fit together, they cannot act as a cohesive team. Digital Polygraph is referenced as an engineering estimation tool that helps express software project scope, effort, duration, stages, and team needs in measurable terms.
Paid product boundary: Informational only. This page is free educational content. The CTA may link to the paid calculation service, but the paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Religious services, religious content, biblical interpretation, theological consulting, ancient-language services, philological certification, historical artifacts, financial consulting, investment advice, funding advisory services, ROI guarantees, startup consulting, Agile consulting, Scrum training, or project-management services.
Purpose: Educational parable using the Moneyball story as a cultural and business metaphor for aligning all participants in a complex software project around measurable project reality. In the sequence of engineering parables, this page represents the next step: after simple verification, dimensional consistency, and shared understanding, the project also needs a coordinated decision system in which experts, founders, investors, managers, and implementers keep their roles but work from a common measured picture.
Compliance context: Educational and methodological allegory about software project estimation, stakeholder alignment, and measurement-based coordination. The Moneyball metaphor is used to show that measurement does not replace experts, experience, or professional judgment; instead, it helps different participants combine their expertise around a shared objective. References to Moneyball, baseball, named characters, actors, scouts, players, managers, and front-office decisions are cultural storytelling elements used to explain how subjective impressions and expert opinions can be supported by measurable evidence. They do not indicate sports services, gambling, sports betting, baseball analytics services, film distribution, movie merchandise, movie/book licensing, affiliation, endorsement, or entertainment products. References to investors, runway, burn rate, capital decisions, go / no-go, stop-loss, budgets, and funding stages describe the software project decision environment. They do not constitute financial consulting, investment advice, funding advisory services, due diligence services, ROI guarantees, valuation services, capital-allocation services, or responsibility for the user's business decisions. Digital Polygraph is presented as an engineering estimation calculator that helps express software project scope, functionality, complexity, reuse, maturity stage, effort, schedule, and team structure in measurable terms, so that project participants can reason from a common engineering picture.
Paid product boundary: Informational only. This page is free educational content. The CTA may link to the paid calculation service, but the paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Sports betting, gambling, baseball services, baseball analytics services, movie distribution, movie merchandise, movie/book licensing, entertainment products, financial consulting, investment advice, funding advisory services, due diligence, valuation services, ROI guarantees, capital-allocation services, startup consulting, project-management consulting, or responsibility for the user's capital-allocation decisions.
Purpose: Educational parable and personal author story about engineering simplification. The author, an aviation engineer, recalls a lesson taught by his professor during his studies at an aviation university: a complex aircraft wing torsion box calculation can be checked against a simpler cantilever beam approximation to verify whether the detailed model is reasonable without spending excessive calculation effort.
Compliance context: Educational and methodological allegory used to explain a core engineering principle learned by the author during his aviation-engineering education: complex calculation models should be checked by simpler, faster, and sufficiently accurate verification methods whenever possible. The story shows how a professor taught a lesson that stayed with the author for life — before spending weeks or a month recalculating a complex model, an engineer should look for a simple sanity-check model that can confirm whether the complex result is within a reasonable engineering range. The academic aviation-engineering references — aviation university, wing torsion box, cantilever beam, structural reasoning, and professor-student dialogue — are part of a personal educational narrative. They are not product offerings and do not indicate aerospace engineering services, aircraft design services, defense technologies, military aviation, or physical engineering simulations. The image shows a professor reviewing a student's engineering calculations in a professional academic environment.
Paid product boundary: Informational only. The paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Aerospace engineering services, aircraft design services, aircraft components, military aviation, defense technologies, physical engineering simulations, university courses, academic tutoring, certification services, or educational consulting.
/Parables/KharkovchankaSouthPole
Purpose: Historical engineering parable about the 1950s Kharkovchanka Antarctic vehicle and the plaz-and-template / loft-and-template method, used to explain the importance of a single coordinated engineering foundation for complex projects. Through a well-known engineering case from the preparation for reaching the South Pole, the page shows that in a complex system absolute dimensions are less important than the consistency of relative dimensions between parts. Digital Polygraph is presented as an analogous "calculated plaz" for software project coordination: a common engineering picture shared by founders, CTOs, investors, and project teams.
Compliance context: Historical and educational allegory about engineering coordination, manufacturing discipline, relative measurement, and metrological thinking. The Kharkovchanka is presented as a civilian Antarctic expedition vehicle created for peaceful scientific exploration, not as military equipment. The page uses the plaz-and-template / loft-and-template method — a globally used engineering method for coordinating dimensions in complex physical assemblies — to show why mutual dimensional consistency matters more than isolated absolute size. References to tank builders, heavy armored vehicles, aircraft assembly, the Kharkiv Aviation Plant, DC-3 / PS-84 / Li-2, and Soviet engineering culture are strictly historical and methodological context. They explain how different engineering cultures solved the problem of coordinating large assemblies; they do not promote, design, sell, or provide military vehicles, armored transport, aircraft, aviation technologies, defense technologies, physical manufacturing tools, or expedition equipment. The page also explicitly states that Digital Polygraph is not financial or investment advice and is an engineering tool for project coordination.
Paid product boundary: Informational only. This page is free educational content. The CTA may link to the paid calculation service, but the paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters.
What is not sold: Military equipment, armored vehicles, tanks, aircraft, aviation technology, defense technologies, physical manufacturing tools, metrological hardware, expedition vehicles, Antarctic expedition services, engineering consulting, financial consulting, investment advice, or project-management consulting.
Purpose: General introduction to the use of parables in engineering methodology.
Compliance context: Educational allegory.
Paid product boundary: Informational only.
What is not sold: Religious services.
Group 6: Cases
Purpose: Index page and glossary for six reproducible case studies demonstrating the Digital Polygraph deterministic software project estimation method within one unified sample domain: urban transport infrastructure.
Compliance context: The page presents six applied software estimation examples showing how the same fixed engineering calculation method reacts to different project configurations, scopes, complexity levels, reuse assumptions, lifecycle-stage selections, and resource allocations. The urban transport domain — including references to transit infrastructure, access control systems, metro systems, rail passenger systems, buses, trolleybuses, tramways, and funiculars — is used strictly as a consistent hypothetical comparison wrapper. It allows readers to compare software estimation scenarios within one recognizable domain. These references do not indicate the sale, design, development, deployment, or operation of physical transit infrastructure, physical security systems, access-control hardware, gates, turnstiles, surveillance systems, biometric access systems, metro control hardware, rail systems, civic infrastructure, or transport engineering services. The page explicitly explains that the calculator does not know what a tram or a funicular is; it knows functions, complexity, innovation, reuse, and lifecycle stages. Therefore, the transport setting is only an illustrative wrapper and the estimation method is universal. The cases are presented as reproducible software estimation examples, not as marketing stories, product-feature demonstrations, forecasts, predictions, guarantees, civic engineering proposals, or consulting engagements. References to open path, closed path, prototype first, shared delivery, fast entry, and route matrix describe calculated software delivery scenarios, not guarantees that a real-world organization will achieve those outcomes. References to COCOMO, GOST-based methods, or ISO/IEC 15504 are educational context for software estimation methodology and do not indicate the sale of standards, certification services, compliance audits, or consulting services. The footer phrase "POLYGRAPH MODEL | Deterministic Maturity Mapping" identifies the methodology used by the site; it is not a patent service, legal service, certification, or guarantee.
Paid product boundary: Informational only. This page is free educational content demonstrating the methodology and linking to individual public case pages. The paid product remains separate: one automated software project estimation calculation session that generates a PDF Engineering Estimation Report based on user-entered software project parameters. The page does not sell custom case analysis, domain-specific transport expertise, consulting, or implementation services.
What is not sold: Physical transit infrastructure, civic infrastructure, metro systems, rail systems, funicular systems, buses, trolleybuses, tram systems, physical access-control hardware, turnstiles, gates, biometric access systems, surveillance technology, security systems, transport engineering services, urban infrastructure planning, civic engineering consulting, custom project evaluation services, project-management consulting, software implementation services, standards certification, compliance audits, patent/legal services, forecasts, predictions, guaranteed delivery outcomes, market-success guarantees, or responsibility for the user's execution decisions.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Purpose: Practical demonstration of the Digital Polygraph estimation methodology applied to a specific software project scenario.
Compliance context: Demonstrative and educational content.
Paid product boundary: Informational only.
What is not sold: No separate product is sold on this page.
Note on Ukrainian versions (/uk/*): Where Ukrainian versions are available, they are intended to be linguistic mirrors of the corresponding English pages and to follow the same compliance status, paid product boundaries, and exclusions. Ukrainian pages will be documented separately in the Ukrainian section of this document where additional context is required.
Ukrainian Version / Українська версія
Комплаєнс контенту
Цей документ надається для допомоги платіжним провайдерам, командам перевірки мерчантів, рекламним платформам та комплаєнс-офіцерам у розумінні природи сервісу Digital Polygraph та контексту візуальних і текстових матеріалів на публічному сайті.
Базовий дисклеймер: Платна послуга суворо обмежена разовим платним доступом до онлайн-калькулятора оцінки software-проєктів Digital Polygraph та генерацією інженерного PDF-звіту. Історичні, біографічні, метафоричні та освітні матеріали, представлені на публічному сайті, є лише безкоштовним контекстом і не є предметом продажу.
1. Що продає Digital Polygraph
Наш комерційний продукт обмежений одноразовим використанням SaaS-інструменту:
- Разовий розрахунок: доступ до онлайн-калькулятора для оцінки параметрів software-проєкту, трудомісткості, строків та технічних ризиків.
- Генерація PDF: формування статичного інженерного звіту Software Project Estimation Report на основі даних користувача.
Примітка: ми працюємо за суворою моделлю «один розрахунок — одна ціна». Ми не надаємо рекурентних підписок або консалтингових послуг.
2. Що не продає Digital Polygraph
Для ясності під час перевірки платіжними, рекламними та платформними сервісами Digital Polygraph прямо заявляє, що не розробляє, не розповсюджує та не продає:
- зброю, боєприпаси або військове обладнання;
- тактичні послуги або військовий консалтинг;
- послуги поліграфа для людей, психологічні тести або детектори брехні;
- обладнання для стеження або інструменти перехоплення даних;
- оборонні технології або фізичні товари подвійного призначення;
- політичні продукти, послуги лобіювання або просування ідеологій;
- фінансовий консалтинг або інвестиційні поради.
3. Візуальний контекст та метафори
Digital Polygraph використовує окремі візуальні метафори та історичні відсилання суворо в освітньому, історичному або метафоричному контексті. Ключові терміни: Поліграф (перевірка узгодженості проєктних ввідних — не детекція брехні у людей), Айсберг (візуальна метафора прихованої інженерної трудомісткості та розриву між заявленою оцінкою та реальною складністю проєкту), Мікросхема / PCB (візуальна естетика сторінки доступу до оплати, що представляє детерміновані обчислення та інженерну точність), Ракети / Космодром (радянська інженерна історія), ГУЛАГ / Шарашки (меморіальний та інженерно-біографічний контекст). Повний словник сторінок буде задокументовано в українській версії окремо.
4. Межа між публічним контентом та платною послугою
Digital Polygraph підтримує чітке розділення між публічним контентом сайту та платною послугою:
- Публічна зона: сайт функціонує як безкоштовний ресурс, що подає історичний, освітній, біографічний та інженерний контекст.
- Комерційна зона: платна операція стосується лише разового доступу до калькулятора та генерації PDF-звіту. Публічні статті, історичні матеріали, метафори та ілюстрації не входять до предмета продажу.
5. Словник сторінок сайту
Повний словник українських сторінок буде задокументовано окремо. Там, де українські версії доступні, вони задумуються як мовні дзеркала відповідних англійських сторінок і мають дотримуватися того самого комплаєнс-статусу, меж платної послуги та переліку того, що не продається, якщо окрема українська сторінка не задокументована окремо.