# Brand Portals for Brands Submission Pack

## Project Name

EvidenceOps Agent Brand Portal

## Primary Submission URL

Use the published BrandKity BrandKit first:

https://brandkity.com/p/zhangmengcheng23s-workspace/evidenceops-agent

## Live Brand Portal Backup

https://1kai123.github.io/evidenceops-agent/brand-portal/

## Published BrandKity BrandKit

https://brandkity.com/p/zhangmengcheng23s-workspace/evidenceops-agent

## Brand Assets Package

https://1kai123.github.io/evidenceops-agent/brand-portal/assets/evidenceops-brand-assets.zip

## QA Report

https://github.com/1kai123/evidenceops-agent/blob/main/BRAND_PORTAL_QA_REPORT.md

## Brand Walkthrough Video

https://1kai123.github.io/evidenceops-agent/brand-portal/assets/video/evidenceops-brand-walkthrough.mp4

## Repository

https://github.com/1kai123/evidenceops-agent

## Copy-Ready Final Fields

Use `BRAND_PORTALS_FINAL_SUBMISSION_FIELDS.md` for the final Devpost form. Devpost eligibility and the BrandKity BrandKit are complete; Brand Devpost access still returns HTTP 403.

## Eligibility Notes

- The hackathon page lists `Students only`.
- The page lists `Above legal age of majority in country of residence`.
- The page lists `All countries/territories, excluding standard exceptions`.
- China is not named in the visible exclusion summary. A China-based student should still be prepared to provide student proof and identity/payment documents if selected.

## Submission Story

EvidenceOps Agent Brand Portal is a complete brand kit for an explainable AI incident response workspace. The product promise is simple: evidence that moves at machine speed and still stands up in review.

The portal includes logo lockups, symbol assets, color system, typography guidance, voice rules, report examples, terminal examples, Devpost/social cover art, and a downloadable brand guidelines document. It is built as a live web brand portal rather than a static moodboard so judges can inspect the actual delivery experience.

The brand direction is forensic, precise, and security-native. It avoids generic AI gradients and instead uses incident-report structure, chain-of-custody labels, evidence IDs, terminal traces, and approval gates. This matches the product itself: an AI incident response agent that cites evidence, labels uncertainty, and requires human approval for disruptive actions.

## Built With

HTML, CSS, JavaScript, SVG, brand design, identity system, product storytelling, cybersecurity, AI agents, incident response.

## Why It Can Compete

- Strong fit with judging criteria: presentation, organization, design quality, consistency, and completeness.
- Complete asset library with downloadable files.
- Distinctive product-contextual design instead of generic brand templates.
- Live portal is easy for judges to inspect.
- The brand system is grounded in an existing working product and public demo.
- The live portal now includes a `Judge Fit` section that maps every official judging dimension to visible proof in the submission.
- PNG cover art and a brand-specific 60-90 second video script are prepared if the submission form requests media uploads.
- A brand-specific 30-second walkthrough MP4 is embedded in the portal and available as a direct supporting URL.

## Judging Criteria Mapping

| Criterion | Evidence in submission |
| --- | --- |
| Presentation | First-screen product promise, case card, evidence trace, and clear artifact links. |
| Organization | Separate sections for assets, visual system, applications, voice, submission package, and BrandKity transfer. |
| Design Quality | Security-native identity based on incident reports, evidence IDs, terminal traces, and approval gates. |
| Consistency | Same logo, color, typography, copy rules, and evidence language across product, report, social, and Devpost assets. |
| Completeness | Live portal, repository, downloadable brand assets package, brand guidelines, QA report, and BrandKity transfer guide. |

## Remaining Risk

The hackathon name implies BrandKity/brand portal tooling may be expected. A BrandKity-hosted BrandKit is now published and should be used as the primary submission URL.

Current blocker: `https://brand.devpost.com/` returns HTTP 403 for the current account/network even after Devpost student eligibility and BrandKity publishing were completed. Devpost support was contacted on 2026-06-11 with the published BrandKity URL, GitHub Pages backup, asset package, QA report, and repository.

BrandKity path completed: Google login succeeded, the `EvidenceOps Agent` BrandKit was created, content and assets were added, and the public BrandKity URL was verified.

Access recovery status and the Devpost support email copy are recorded in `BRAND_PORTALS_ACCESS_RECOVERY.md`.