التنفيذ
يُنفّذ heroic-project أوامر اختبار الاختراق على الشبكة المصرّح بها، ويطبّق إجراءات حماية الشبكة — الهجوم والدفاع وجهان لأداة واحدة.
- TARGETالهدف المحدد
- ACTIONاختبار اختراق
- GUARDإجراء حماية
heroic-project is a cybersecurity operations system dedicated to executing penetration-testing commands and protecting networks. Its defining entry behavior is environmental: the site displays the Wi‑Fi networks near the user, subjects them to AI-driven inspection, and reports an analysis that must be correct, realistic, and not fabricated.
The product intent derived from the authoritative requirement thread is therefore threefold and inseparable:
The audience is a single accepted active human role: a cybersecurity user / penetration tester operating in Arabic-speaking markets, working in a dark operations-console environment where the interface behaves like a live instrument reporting truth rather than a marketing surface. The hard constraint that analysis must be real and non-fabricated governs the entire information architecture: observed evidence and inferred verdict are never merged, and every number shown must trace to an observation.
heroic-project is delivered as a first-party web application with custom UI. There is no sign-up, no login, and no account creation: the system works end-to-end immediately («يعمل على الطول») and begins directly with scanning networks and vulnerabilities. The operator opens the application and is already inside the operations console.
Current delivery and actors
Accepted behavior
Narrow exclusions
Delivery ownership. heroic-project is a first-party web application. All nine accepted surfaces are application-owned custom pages. The scan and analysis work is executed by an application backend; the operator interacts with it through the AI Scan and Analysis surfaces, never directly.
Access ownership. There is no identity layer. No sign-up, login, or account-creation surface exists, and no session is required to reach any surface. Landing, Networks, AI Scan, Analysis, Penetration Testing, and Network Protection are all reachable directly, and the system begins scanning networks and vulnerabilities immediately on entry. Scan history, analysis results, penetration-testing executions, and protection actions remain available to the operator on the device without an account gate.
Current vs. future boundary. Everything described in this document is current. No future-horizon capabilities were accepted in the authoritative thread; nothing is deferred, and nothing outside the accepted behavior is planned here.
Truth boundary. The no-fabrication constraint is a delivery boundary, not a stylistic preference. The system reports what was observed and separately reports what was inferred, with the inference citing the observations it used. Where an observation is unavailable, the system says so rather than filling the gap. The system never displays fake or virtual networks: every row, blip, and counter is produced from a real observation of the operator's environment, and when real observation is unavailable the system states that unavailability instead of rendering simulated networks.
Not applicable — no reference directive in this project declares content_source authority, so no source content inventory is rendered.
FR-1 — Nearby Wi‑Fi network display As a مستخدم أمن سيبراني / مختبر اختراق I should see the Wi‑Fi networks near me listed with their identifying and signal attributes so that I can choose a real target to examine.
FR-2 — AI scan of a selected network As a مستخدم أمن سيبراني / مختبر اختراق I should run an AI-based scan against a specific nearby network so that the network is actually inspected rather than merely listed.
FR-3 — Realistic, non-fabricated analysis As a مستخدم أمن سيبراني / مختبر اختراق I should receive an analysis that is correct and realistic and not fabricated so that I can act on it with confidence.
FR-4 — Penetration-testing command execution As a مستخدم أمن سيبراني / مختبر اختراق I should execute penetration-testing commands against a target network so that I can carry out the offensive testing the system exists to perform.
FR-5 — Network protection action execution As a مستخدم أمن سيبراني / مختبر اختراق I should apply network-protection actions to a network so that I can defend the networks the system has analyzed.
FR-6 — Self-service identity establishment As a مستخدم أمن سيبراني / مختبر اختراق I should create my own account on first use so that my scans, analyses, tests, and protections are privately owned and resumable.
FR-7 — Returning verification As a مستخدم أمن سيبراني / مختبر اختراق I should verify my identity on return so that I regain access to my scan, testing, and protection work.
FR-8 — Backend execution of scan and analysis As a مستخدم أمن سيبراني / مختبر اختراق I should have the scan and analysis executed by a backend capable of producing correct, realistic, non-fabricated results so that the output I read is grounded in real observation.
Product context. This operator works inside heroic-project as an instrument panel for live Wi‑Fi discovery, AI-driven vulnerability analysis, and offensive/defensive command execution. They operate in Arabic RTL, in a dark console environment, often at night, and they need the interface to report truth rather than to persuade. The product's whole reason for existing is that this operator must be able to trust what the screen says.
Primary goal. Discover the Wi‑Fi networks physically near them, obtain a correct and realistic AI analysis of a chosen network, and then execute the penetration-testing commands and network-protection actions that the analysis justifies.
Distinct accepted responsibilities.
Relevant inputs and decisions.
Interactions with other accepted participants. There are no other accepted human participants in the current scope. The operator's counterpart is the application backend, which performs the scan and analysis and returns observations and a verdict. The operator's relationship to it is one of audit: the backend must show its evidence, and the operator must be able to check the verdict against it. The operator also interacts with the identity surfaces (Sign Up, Login) as a prerequisite to protected work, but those are access boundaries rather than collaborators.
Observable success. The operator sees a real list of nearby networks, obtains an analysis whose every number traces to a visible observation, executes penetration-testing commands and protection actions whose outcomes are recorded truthfully as success or failure, and can leave and return to find their work intact.
What makes this role's work different. This is not a passive dashboard reader. The operator's work alternates between two channels that the interface keeps visually and semantically distinct: passive observation (cyan telemetry — what the system is seeing) and active execution (amber commands — what the system is about to do). The operator must be able to tell at a glance which mode they are in, because one is reading and the other is acting on a live network. Their defining constraint is that they cannot tolerate a fabricated result: a wrong reading in this role is worse than no reading.
Muse: Gleb Kuznetsov. Headline direction: Cinematic future tech for offensive and defensive network operations — a live instrument reading a hostile environment, not a marketing surface.
| Role | Hex | Usage |
|---|---|---|
| Background (void ground) | #05070C | Carries ~70% of every screen |
| Surface (panel) | #0B1018 | Panels at 0.92 opacity so the void shows through faintly |
| Text | #E8EEF5 | Body text at 15–16px on the void ground (~14:1 contrast) |
| Primary (cyan signal) | #22E0FF | Passive telemetry, network blips, safe/encrypted states, focus rings, active nav |
| Accent (amber) | #FF8A1E | Reserved exclusively for offensive/active actions and unencrypted-network warnings |
| Muted | #5A6B7D | Metadata, timestamps, secondary labels — never for anything the user must read to act |
| Panel border | rgba(34,224,255,0.18) | 1px luminous border on every panel |
| Glow | 0 0 24px rgba(34,224,255,0.15) | Depth source; no drop shadows anywhere |
Cyan sits at hue 187, deliberately outside the forbidden blue-indigo band. No blue-indigo (#2563EB, #6366F1, #7C3AED) appears anywhere. Amber's appearance on screen is itself information: any amber pixel means an offensive command is available or was executed.
#5A6B7D.clamp(48px, 8vw, 112px). Section headings: clamp(28px, 4vw, 48px). Body: 16px / 1.6 line-height. Arabic body: same scale with 1.75 line-height for diacritic clearance.Thin luminous strokes and glass. Panels are 12px-radius rounded rectangles with a 1px rgba(34,224,255,0.18) border and a #0B1018 fill at 0.92 opacity. Radial gauges and concentric rings carry signal strength and threat scoring. Actionable command cards use 45° chamfered corners — cut, not rounded — to distinguish "this executes something" from "this displays something". No drop shadows; depth comes from glow and layering, never from grey blur.
Full-bleed dark canvas with a persistent left rail (72px collapsed, 264px expanded) holding icon+label navigation in Arabic RTL: الشبكات، الفحص، التحليل، اختبار الاختراق، الحماية. Content is a modular HUD grid. On the hero, the radar sweep is the dominant element at 60% width with a right-hand vertical telemetry stack. Networks is a dense ruled table (SSID / BSSID / CH / RSSI / CIPHER / RISK) with a live sparkline column, not cards. Analysis uses a two-column split — evidence on the right, AI verdict on the left — never merged. At 375px the rail collapses to a bottom tab bar, the radar becomes a vertical list, and the table becomes stacked ruled rows with label/value pairs.
No stock photography, no illustration. Imagery is generated from the product's own data: a canvas radar field with network blips positioned by real bearing and RSSI, concentric range rings labelled in metres, and faint topographic contour lines for physical-space context. Network detail views show a channel-occupancy waterfall (2.4/5/6 GHz bands as stacked rows, occupied channels lit cyan, congested channels amber). Threat scores render as a radial gauge with a needle, never a progress bar. Icons are 1.5px-stroke line pictograms in the HUD style.
Headlines, wordmarks, labels, numbers, cards, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit, with no other element covering any part of them. Crops, bleeds, and off-edge placement are reserved for decoration only — shapes, textures, rules, and background art. Moving and scrollable content may cross the viewport edge by design, but every item must become fully readable as it passes; under prefers-reduced-motion it stops and shows whole items, wrapping into rows or sitting in a horizontally scrollable row (overflow-x: auto).
The radar is the hero, and the type sits inside the instrument.
The public entry is a full-bleed void-black canvas (#05070C) whose dominant element is a live radar field: concentric cyan rings on a 1px grid, a rotating sweep arm at a 6-second period, and network blips placed at their real bearing and radius-by-RSSI. This is the product's own sensor output rendered as the first thing anyone sees — not a claim about the product, but the product observing.
The headline is set in Space Grotesk at clamp(48px, 8vw, 112px), Arabic first for the primary audience, positioned in the upper-right quadrant of the grid rather than centred, with the second line offset left by two columns to break the axis. Below it, a single amber chamfered command card reads «ابدأ الفحص», cut into the composition at the 7th column. To the far left, a vertical telemetry strip shows live counters — networks seen, encrypted, open, high-risk — in IBM Plex Mono tabular figures.
The composition deliberately refuses the centred headline + subtext + single CTA template. There is no gradient blob, no centred stack, and no blue button. The radar occupies the field; the type is placed into it as an instrument annotation. The amber card is the only amber element on the surface, which means its presence alone signals that an action is available — the colour system is doing operational work from the very first screen.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: layered_2d
Focal subject. The live radar field: concentric cyan range rings on a 1px void grid, a rotating sweep arm at a 6-second period, and network blips placed at their real bearing and radius-by-RSSI, with a vertical telemetry strip of monospace counters at the far left.
Input → transformation → outcome thesis. Real nearby-network observations enter the system → the sweep arm passes over each network's bearing and the blip fades in at its radius-by-RSSI while the telemetry counters count up to their real values → the operator sees the product's own sensor output as the first frame, and the amber «ابدأ الفحص» card becomes the single available action.
Motion vocabulary. Continuous slow radar sweep (6s rotation) with blips fading in as networks are discovered; numbers counting up on reveal (RSSI, channel, threat score) in monospace tabular figures so nothing reflows; scroll-scrubbed parallax on the hero's concentric rings at 0.3x; command execution shown as a horizontal scan-line sweep across the card while running, terminating in either a cyan complete pulse or an amber action-required pulse.
Composed first frame. Void-black ground. Concentric cyan rings drawn on the grid with the sweep arm mid-rotation. Blips already placed at their real positions. The Arabic headline in the upper-right quadrant with its second line offset left. The amber chamfered command card cut in at the 7th column. The telemetry strip at the far left holding its counters at zero, about to count up.
Reduced-motion state. Under prefers-reduced-motion, the radar freezes as a static concentric diagram with blips placed at their final positions, counters jump directly to their final values, and scan-lines become a static progress bar. No information is lost — the instrument simply stops moving.
NFR-1 — Analysis truthfulness (hard constraint) The analysis produced by the system must be correct and realistic and must not be fabricated. No placeholder, simulated, or invented scan result may be presented as real. Every number displayed in a verdict must trace to an observation shown in the evidence column. Where an observation is unavailable, the system states its unavailability rather than filling the gap.
NFR-2 — Evidence/verdict separation The Analysis surface must keep raw observations and the AI verdict in separate, non-merged columns, with the verdict citing the specific observations it used and a confidence figure.
NFR-3 — Backend capability for real results Scan and analysis execution must run through a backend capable of producing correct, realistic, non-fabricated results.
NFR-4 — Identity continuity for protected work Scan history, analysis results, penetration-testing executions, and protection actions must remain bound to the correct operator and resumable across sessions.
NFR-5 — Access boundary integrity Landing, Sign Up, and Login are reachable without a session. Dashboard, Networks, AI Scan, Analysis, Penetration Testing, and Network Protection require login. No protected destination owns the interaction that grants access to itself.
NFR-6 — Readability at every viewport Headlines, wordmarks, labels, numbers, cards, and controls must remain entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, with no other element covering any part of them.
NFR-7 — Reduced-motion compliance
All motion must honour prefers-reduced-motion: the radar freezes as a static concentric diagram with blips placed, counters jump to final values, and scan-lines become a static progress bar.
NFR-8 — Arabic RTL operation The interface operates in Arabic RTL, with the left rail holding icon+label navigation in Arabic and Arabic body text set at 1.75 line-height for diacritic clearance.
No source-specified technology was overridden. The stack above preserves the accepted delivery shape (first-party custom UI with application-owned identity and backend integration) and introduces no adjacent capability.
Assumptions
[Required inference] The operator has a device capable of observing nearby Wi‑Fi networks, and the application can obtain that observation. If observation is unavailable, the system reports the failure rather than fabricating networks.[Required inference] Self-service registration is the correct identity bootstrap because the source specifies no invitation, provisioning, or deployment-based onboarding.[Required inference] The backend is the sole producer of scan observations and analysis verdicts; the frontend never invents or interpolates a result.[Default — not specified by user] The application is delivered as a web application with a persistent left rail that collapses to a bottom tab bar at 375px.Constraints
#2563EB, #6366F1, #7C3AED) must not appear anywhere; cyan stays at hue ~187. (explicit)#5A6B7D is never used for anything the user must read to act. (explicit)
heroic-project — WIRELESS OBSERVATION
يعرض heroic-project الشبكات القريبة منك ويعرض القراءات كما وردت من المستشعر — القناة والتشفير وقوة الإشارة — ثم يفحصها بالذكاء الاصطناعي ويقدّم تحليلًا واقعيًا. إن لم تتوفر قراءة، يقول النظام ذلك بدلًا من اختراعها.
heroic-project يعرض الشبكات اللاسلكية القريبة منك، ويفحصها بالذكاء الاصطناعي، ثم ينفّذ أوامر اختبار الاختراق وإجراءات حماية الشبكة. التحليل مبنيّ على القياسات المرصودة، صحيح وواقعي وغير وهمي.
يُنفّذ heroic-project أوامر اختبار الاختراق على الشبكة المصرّح بها، ويطبّق إجراءات حماية الشبكة — الهجوم والدفاع وجهان لأداة واحدة.
يقرأ heroic-project الشبكات اللاسلكية المحيطة فعليًا، ويُدرج كل شبكة بمعرّفها وخصائصها المقيسة كما رصدها المستشعر — دون تقدير أو استنتاج.
تُفحص الشبكة المختارة فحصًا آليًا، فيُبنى التحليل على القياسات المرصودة نفسها. النتيجة صحيحة وواقعية، ويسرد التحليل الأدلة التي استند إليها.
الملاحظات الخام تُعرض في عمودها الخاص وحدها: اسم الشبكة، وعنوانها الفيزيائي، والقناة، وشدّة الإشارة، ونوع التشفير، ووقت الرصد. أمّا حكم الذكاء الاصطناعي فيظهر في عمود منفصل، ولا يُدمج الاثنان في قراءة واحدة أبدًا.
كل حكم يذكر الملاحظات التي استند إليها بالاسم، ويُرفق معه رقم ثقة يوضّح مقدار ما بُني عليه.
الملاحظات الخام
ما رصده المستشعر فعليًا، معروضًا كما هو دون تفسير ودون إكمال أي قيمة ناقصة.
حكم الذكاء الاصطناعي
قراءة مشتقّة من الملاحظات نفسها، تذكر ما استندت إليه من ملاحظات.
وحين لا تتوفّر ملاحظة، يقول النظام ذلك صراحةً ولا يملأ الفراغ بتقدير أو قيمة مفترضة.

heroic-project — WIRELESS OBSERVATION
يعرض heroic-project الشبكات القريبة منك ويعرض القراءات كما وردت من المستشعر — القناة والتشفير وقوة الإشارة — ثم يفحصها بالذكاء الاصطناعي ويقدّم تحليلًا واقعيًا. إن لم تتوفر قراءة، يقول النظام ذلك بدلًا من اختراعها.
heroic-project يعرض الشبكات اللاسلكية القريبة منك، ويفحصها بالذكاء الاصطناعي، ثم ينفّذ أوامر اختبار الاختراق وإجراءات حماية الشبكة. التحليل مبنيّ على القياسات المرصودة، صحيح وواقعي وغير وهمي.
يُنفّذ heroic-project أوامر اختبار الاختراق على الشبكة المصرّح بها، ويطبّق إجراءات حماية الشبكة — الهجوم والدفاع وجهان لأداة واحدة.
يقرأ heroic-project الشبكات اللاسلكية المحيطة فعليًا، ويُدرج كل شبكة بمعرّفها وخصائصها المقيسة كما رصدها المستشعر — دون تقدير أو استنتاج.
تُفحص الشبكة المختارة فحصًا آليًا، فيُبنى التحليل على القياسات المرصودة نفسها. النتيجة صحيحة وواقعية، ويسرد التحليل الأدلة التي استند إليها.
الملاحظات الخام تُعرض في عمودها الخاص وحدها: اسم الشبكة، وعنوانها الفيزيائي، والقناة، وشدّة الإشارة، ونوع التشفير، ووقت الرصد. أمّا حكم الذكاء الاصطناعي فيظهر في عمود منفصل، ولا يُدمج الاثنان في قراءة واحدة أبدًا.
كل حكم يذكر الملاحظات التي استند إليها بالاسم، ويُرفق معه رقم ثقة يوضّح مقدار ما بُني عليه.
الملاحظات الخام
ما رصده المستشعر فعليًا، معروضًا كما هو دون تفسير ودون إكمال أي قيمة ناقصة.
حكم الذكاء الاصطناعي
قراءة مشتقّة من الملاحظات نفسها، تذكر ما استندت إليه من ملاحظات.
وحين لا تتوفّر ملاحظة، يقول النظام ذلك صراحةً ولا يملأ الفراغ بتقدير أو قيمة مفترضة.
No comments yet. Be the first!