Skip to content

Turn GOOSE Analyzer and SCL Workspace into bilingual practical tutorials - #119

Merged
masarray merged 6 commits into
mainfrom
agent/capability-tutorials-goose-scl
Jul 29, 2026
Merged

Turn GOOSE Analyzer and SCL Workspace into bilingual practical tutorials#119
masarray merged 6 commits into
mainfrom
agent/capability-tutorials-goose-scl

Conversation

@masarray

@masarray masarray commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Purpose

Continue the ARSAS Learning Center transformation by converting the GOOSE Analyzer and SCL Workspace pages into practical, search-friendly tutorials in English and Indonesian.

GOOSE Analyzer tutorial

Rewrites goose-analyzer.html and analyzer-goose-iec61850.html around publisher identity, APPID/VLAN/MAC/goCBRef, stNum, sqNum, retransmission, Time Allowed to Live, flags, payload mapping and passive-capture boundaries.

The six-step workflow covers capture authority, approved adapter selection, publisher identification, steady-state sequence, one approved state change, payload mapping and evidence recording.

SCL Workspace tutorial

Rewrites scl-workspace.html and workspace-scl-iec61850.html around the practical roles of ICD, CID, SCD, IID and SSD, configured intent versus live evidence, receiving-system requirements, bounded output and importer validation.

Learning and SEO structure

Each page now includes:

  • a 30-second takeaway
  • when-to-use guidance
  • prerequisites and authority boundaries
  • plain-language protocol concepts
  • six ordered practical steps
  • success criteria
  • failure-oriented troubleshooting
  • three visible FAQ items
  • reciprocal EN/ID paths
  • Learning Center continuation
  • TechArticle, HowTo, FAQPage and BreadcrumbList structured data

Engineering honesty

Publisher capture is not presented as proof of subscriber operation, trip timing or end-to-end protection acceptance. Valid XML or schema-aware SCL output is not presented as proof of receiving-tool acceptance, project-wide correctness or IEC 61850 conformance.

Automated contracts

Source and deployment validators now enforce the bilingual GOOSE/SCL pairs, six steps, three FAQs, required success/failure sections, structured data and Learning Center paths while preserving all existing onboarding, IO FAT, evidence, compatibility, demo, issue-intake and supply-chain checks.

Automated validation at head 3a002eb0fb354d46d24ca6e8defd1b539253531f

Deploy product website run 162 — success

  • source and rendered product validation
  • deterministic 62-page build
  • reciprocal hreflang and sitemap
  • metadata and structured data
  • contextual authority graph
  • responsive media
  • internal links and fragments
  • IndexNow dry-run and public-boundary checks

Validate adoption and field proof run 52 — success

  • bilingual GOOSE and SCL tutorial contracts
  • six-step and three-FAQ requirements
  • Learning Center, Quick Start, IO FAT, evidence, compatibility, demo and supply-chain boundaries

Build search growth queue run 61 — success

  • authority graph validation
  • structural search queue
  • internal-link coverage
  • growth evidence artifact

Build ARSAS run 778 — success

  • source, website, license and UX invariants
  • immutable ARIEC61850 engine checks
  • full solution restore and build
  • complete application regression tests
  • portable Windows x64 publication and artifact upload

Additional gates — success

  • Measure product website run 70
  • Verify production website health run 87

@masarray
masarray marked this pull request as ready for review July 29, 2026 02:22
@masarray
masarray merged commit 22387b4 into main Jul 29, 2026
12 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3a002eb0fb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +44 to +46
lower = text.lower()
for value in values:
if value.lower() not in lower:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve case-sensitive contract checks

When this helper validates structural tokens, lowercasing both operands allows invalid downstream syntax to pass—for example, packageVerificationCode can become packageverificationcode, or a GitHub issue-form body: key can become Body:. The calls at lines 243 and 256 previously used exact matching because YAML/JSON keys and SPDX values are case-sensitive, so retain exact matching for those contracts or add an explicit case-sensitive mode while folding only prose checks.

Useful? React with 👍 / 👎.

Comment on lines +5 to +6
<title>IEC 61850 GOOSE Analyzer Tutorial — stNum, sqNum and TAL | ARSAS</title>
<meta name="description" content="Learn IEC 61850 GOOSE in plain language and use ARSAS to identify publishers, inspect APPID and VLAN, understand stNum and sqNum, verify TAL and map payloads to SCL." />

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Refresh sitemap dates for the rewritten tutorials

When these rewritten pages are built, write_sitemap copies their lastmod values from landing/site.json, but this commit leaves the GOOSE pair dated 2026-07-20 and the SCL pair dated 2026-07-27 despite replacing their content on 2026-07-29. The generated sitemap therefore advertises materially new tutorials as older versions, weakening the recrawl signal for this search-focused change; update all four registry entries with the rewrite date.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant